ISSUE 864 Fix primitive id field RSQL filter #866
Merged
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.
In #814, INFIX, POSTFIX and PREFIX RSQL filters are supported for Number.class. But for primitive classes, the check
Number.class.isAssignableFrom(relationshipType)
would not work.Possible Solution
Steps to Reproduce (for bugs)
Create a class with id field type
long
and run a filterid=="*1*"
on that would returnInvalidValueException: Invalid value: *1*