TextIndex cannot be created when @Document contains collation specified [DATAMONGO-2316]

[spring-projects-issues]

dmarko484 opened DATAMONGO-2316 and commented

When POJO is annotated with @Document + collation specified (e.g. below) now when there is a field annotated as 8@TextIndexed this index is not created during application start with error as below. Seems that index is being created with collation info but this option is not available for TextIndex, so it fails.

@Document(collection = "custPerson", language = "en", collation = "cs")
public class Person {
  @TextIndexed String firstname;
}

Error we are getting in this situation:

Nested exception is com.mongodb.MongoCommandException: Command failed with error 67 (CannotCreateIndex): 'Index type 'text' does not support collation: \{ locale: "cs", caseLevel: false, caseFirst: "off", strength: 3, numericOrdering: false, alternate: "non-ignorable", maxVariable: "punct", normalization: false, backwards: false, version: "57.1" }'

 

 

---

Affects: 2.2 RC1 (Moore)

Reference URL: https://docs.mongodb.com/manual/core/index-text/#collation-option

[spring-projects-issues]

dmarko484 commented

Christoph Strobl I just forked spring-data-mongodb repo and opened in IntelliJ but have some basic compilation issues with org.springframework.data.mongodb.repository.QPerson (and QAddress, QUser) as not existing. What I'm missing here? I wanted to  create a pull request with fix ... but no chance :)

[spring-projects-issues]

Christoph Strobl commented

dmarko484 This can happen from time to time. Please build it on the command line so that the Querydsl plugin kicks in. IntelliJ should then be able to locate the generated classes.

[spring-projects-issues]

Mark Paluch commented

From the MongoDB docs:

Collation Option
text indexes only support simple binary comparison and do not support collation.

To create a text index on a a collection that has a non-simple collation, you must explicitly specify {collation: {locale: "simple"} } when creating the index.

Setting the collation in the index options seems to address the issue

[spring-projects-issues]

Mark Paluch commented

Fixing the issue requires some indication from Spring Data whether we have to provide the simple collation. Specifying the collation unconditionally will fail on MongoDB versions prior to 3.4, where collations were introduced. We're using the @Document(collation = …) setting to determine whether the collection has a non-simple collation