spring-projects / spring-projects/spring-data-commons

Multi-store support reports `Could not safely identify store assignment`

Open
#3,179 3 comments 1 reaction 1 assignee View on GitHub

@mp911de is already working on this.

Since Sep 23, 2025.

type: enhancement
Dominant language
Java
Stars
838
Forks
730
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.