Added the NUMERIC_IN query clause to manage the Spring-like methods '… #645
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
feat(query): add
NUMERIC_IN
query clause for Redis repository 'In' methodsfix(indexing): enable
@NumericIndexed
type for@Id
fields without schema duplication errorQuery
Introduced support for the
NUMERIC_IN
query clause to handle Spring Data style repository methods ending with 'In'.This enables querying Redis repositories using a collection of numeric values, improving parity with Spring Data JPA query method conventions and enhancing developer ergonomics.
Example:
Indexing
Previously, configuring an
@Id
field with the@NumericIndexed
index type was technically possible but caused index creation to fail with:This happened because the Id field was already implicitly added to the index schema, and explicitly declaring it as
@NumericIndexed
created a duplicate entry.Now, the check also considers
@NumericIndexed
in the “already indexed” list, so it won’t add it twice.