Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve error reporting for not supported repository interfaces [DATACMNS-1174] #1616

spring-projects-issues opened this issue Sep 24, 2017 · 0 comments
in: repository type: enhancement


Copy link

spring-projects-issues commented Sep 24, 2017

Mark Paluch opened DATACMNS-1174 and commented

Composing a repository from Spring Data-provided interfaces that are not supported (due to their nature or not implemented by a particular store) causes confusing exceptions like

  • PropertyReferenceException: No property findAll found for type Person
  • PropertyReferenceException: No property save found for type Person

These cases occur in following arrangements:

  • Declaring a reactive Spring Data JPA repository
  • Declaring a Querydsl repository in a store not supporting Querydsl
  • Declaring PagingAndSortingRepository in a Spring Data for Apache Cassandra repository

In such case, we should rather report that the repository is not supported because we have no implementation for the repository interface fragment which causes the issue and not because we can't derive a query

Affects: 2.1 RC1 (Lovelace), 2.0.9 (Kay SR9)

Issue Links:

  • DATACASS-498 Exception when trying to use PagingAndSortingRepository - findAll not found in (domain object)

  • DATACMNS-1389 RepositoryConfigurationExtensionSupport.useRepositoryConfiguration(...) fails in strict configuration mode

Referenced from: pull request #303

Backported to: 2.0.10 (Kay SR10)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
in: repository type: enhancement
None yet

No branches or pull requests

2 participants