You can use the @DBRef annotation to persist the referenced class in a separate collection, else the document will be persisted in the same document (json). The use of DBRef require an extra query for the mongodb driver, you should consider this to analyze performance issues. From spring data documentation @DBRef – applied at the … Read more
There is no explicit support for that, no. But you should be able to configure that just fine via the uri parameter. We’ve actually updated the documentation recently.
The only way you can currently achieve this is by annotating your domain class with @Document using the collection property to define the name of the collection instances of this class shall be persisted to. However, there’s a JIRA issue open that suggests adding a pluggable naming strategy to configure the ways class, collection and … Read more
An update for 2018 and Spring Boot 2. First of all, you can have data-only integration tests with the embedded db as per the documentation. This uses the DataMongoTest annotation. This configures only the necessary dependencies that make mongoDB tests possible. If you want to do full integration tests, add the AutoConfigureDataMongo annotation instead: @RunWith(SpringRunner.class) … Read more
Actually, the other answer is wrong. It is possible to do a lookup on a DBref field within your aggregator, and you don’t need mapreduce for that. Solution db.A.aggregate([ { $project: { B_fk: { $map: { input: { $map: { input:”$bid”, in: { $arrayElemAt: [{$objectToArray: “$$this”}, 1] }, } }, in: “$$this.v”}}, } }, { … Read more
It’s true that the MongoTemplate doesn’t have findXXX with Pageables. But you can use the Spring Repository PageableExecutionUtils for that. In your example it would look like this: Pageable pageable = new PageRequests(page, size); Query query = new Query().with(pageable); List<XXX> list = mongoTemplate.find(query, XXX.class); return PageableExecutionUtils.getPage( list, pageable, () -> mongoTemplate.count(Query.of(query).limit(-1).skip(-1), XXX.class)); Like in the … Read more
I was to add exclusion annotation to my main annotated class, i.e. instead of @SpringBootApplication I should have @SpringBootApplication @EnableAutoConfiguration(exclude={MongoAutoConfiguration.class})
Disclaimer: I am the lead of the Spring Data project, so I’ll mostly cover the Spring Data side of things here: I think the core distinction between the two projects is that the Hibernate OGM team chose to center their efforts around the JPA while the Spring Data team explicitly did not. The reasons are … Read more
So here’s the story: we add the type by default as some kind of hint what class to instantiate actually. As you have to pipe in a type to read the document into via MongoTemplate anyway there are two possible options: You hand in a type the actual stored type can be assigned to. In … Read more
go to mongoDB console and delete your current user & set authSchema version to 3 instead of 5 , follow these commands in mongo console – mongo use admin db.system.users.remove({}) <== removing all users db.system.version.remove({}) <== removing current version db.system.version.insert({ “_id” : “authSchema”, “currentVersion” : 3 }) Now restart the mongod and create new user … Read more