This is how I do it: @SpringBootApplication(exclude = { MongoAutoConfiguration.class, MongoDataAutoConfiguration.class }) or as suggested by Dan Oak: spring.autoconfigure.exclude= \ org.springframework.boot.autoconfigure.mongo.MongoAutoConfiguration,\ org.springframework.boot.autoconfigure.data.mongo.MongoDataAutoConfiguration
In 3.2 this is possible. First project so that myField contains only the last element, and then match on myField. db.collection.aggregate([ { $project: { id: 1, myField: { $slice: [ “$myField”, -1 ] } } }, { $match: { myField: “myValue” } } ]);
As at MongoDB 3.4, the text search feature is designed to support case-insensitive searches on text content with language-specific rules for stopwords and stemming. Stemming rules for supported languages are based on standard algorithms which generally handle common verbs and nouns but are unaware of proper nouns. There is no explicit support for partial or … Read more
“Convenient” and “powerful to use” are contradicting goals to some degree. Repositories are by far more convenient than templates but the latter of course give you more fine-grained control over what to execute. As the repository programming model is available for multiple Spring Data modules, you’ll find more in-depth documentation for it in the general … Read more