feat: jsonpath predicate support #41
Merged
+309
−22
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.
path_match
function (supporting@@
andjson_path_match
for Tracking: JSON functions and operators databend#11270);Here I've tried to achieve the same behaviour of predicates like postgres has:
Selector::select
returnstrue
orfalse
in jsonb format;json_path_exists
always returnstrue
on predicates, because selector always has the result on it (true
orfalse
)@
is forbidden in predicate expression;I've found the good explanation here https://justatheory.com/2023/10/sql-jsonpath-operators/