Repository navigation
Querying #41334
Replies: 1 comment
|
Moving / expanding a pr comment here as per @stianst
What fields would you not want to be searchable?
In situations where logical operations take place after filtering you have to be careful. Partial push-down of predicates means you can't also pushdown limit / offset, or grouping should that ever need to be supported. You could also consider having formal parameters for things that are indexed, rather than looking for them in the q parameter.
There is subtlety here. Reflection / toString may not capture the actual Jackson mapping. And it flattens the type model - everything is a string, which may be problematic for numerical values - especially floating point numbers or if we introduce greater than / less than. You could entertain simply supporting json path predicates on top of the result rather than a custom query syntax. Of course json path could be used for projection as well. Other thoughts:
|
Uh oh!
There was an error while loading. Please reload this page.
See #41333.
All reactions