spring-projects
Multi-store support reports `Could not safely identify store assignment`
2024-10-15T19:40:08.435+09:00 INFO 11388 --- [ restartedMain] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.avengers.yoribogo.recipe.repository.RecommendedMenuRepository; If you want this repository to be a Redis repository, consider annotating your entities with one of these annotations: org.springframework.data.redis.core.RedisHash (preferred), or consider extending one of the following types with your repository: org.springframework.data.keyvalue.repository.KeyValueRepository
Spring Data JPA - Could not safely identify store assignment for repository candidate interface com.avengers.yoribogo.notification.weeklypopularrecipe.repository.WeeklyPopularRecipeMongoRepository; If you want this repository to be a JPA repository, consider annotating your entities with one of these annotations: jakarta.persistence.Entity, jakarta.persistence.MappedSuperclass (preferred), or consider extending one of the following types with your repository: org.springframework.data.jpa.repository.JpaRepository
Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.avengers.yoribogo.recipe.repository.RecommendedMenuRepository; If you want this repository to be a MongoDB repository, consider annotating your entities with one of these annotations: org.springframework.data.mongodb.core.mapping.Document (preferred), or consider extending one of the following types with your repository: org.springframework.data.mongodb.repository.MongoRepository
There was a problem with the method I created to test the like function. This error is a warning message that did not occur before adding the Insert feature for Mongodb to one transaction. In addition, the functional test also passed as postman. However, after creating an event processing feature to insert data into Mongodb, such a warning statement occurs. Even though there is a warning, the api still works fine. But I don't think that problem has been fundamentally solved. Entities and Document Annotations are appropriately specified in the class I don't think this is enough. Please let me know the cause and solution of this problem
below : my Project File yoribogo.zip
First of all, the issue report has a terrible formatting that makes it almost impossible to read. While I appreciate that there is a reproducer, it contains all of your application instead of the necessary bits to reproduce the issue which makes it again hard to reproduce, in addition this is just a chunk instead of the full project.
You have a point that in a multi-store arrangement, there are multiple messages from modules that report they cannot implement a repository and that can be annoying. For the time being, please specify base packages with your @Enable…Repositories annotation.
Hi @mp911de, here's a mongo and jpa repositories extending @JpaRepository<(Some Jpa Entity), Long> where the Some Jpa Entity is annotated with @Entity. So both the repository extending the JpaRepository as well as the @Entity annotation, according to the documentation should aid in spring determining the repository store safley.
Second, there's a very simple MongoRepository example where we still get the warning.
Specifiying the basePackage for scanning resolves the logs; however, this isn't an option in some projects where organization is by Domain, i.e. controller, service, entity, repository classes are all packaged together based on the domain.
https://github.com/pdibenedetto/springboot-jpa-mongo-issue
