Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.4 M1 (Dijkstra)
-
Spring + GemFire 7.0.2
Description
Presently, when a Spring Data GemFire user defines a GemFire Repository interface extension query, such as...
List<Person> findDistinctByFirstNameEqualOrderByLastNameAsc(String firstName);
The OrderBy clause is completely ignored and the "statically" generated Sort meta-data is not applied to the generated GemFire OQL Select Query.
Furthermore, if a user defines a query interface method with a org.springframework.data.domain.Sort parameter, like so...
List<Person> findDistinctByLastName(String lastName, Sort orderBy);
The Sort parameter is ignored and not used when generating the OQL Select Query.