Update documentation for JSON Index with latest enhancements #334
Conversation
| Find all persons who have at least one address that is not in the US: | ||
|
|
||
| ```sql | ||
| SELECT ... | ||
| FROM mytable | ||
| WHERE JSON_MATCH(person, '"$.addresses[*].country" != ''us''') | ||
| ``` |
There was a problem hiding this comment.
@Jackie-Jiang should we explicitly call out that this semantic is different in previous versions?
There was a problem hiding this comment.
We can add a note stating exclusive predicate doesn't work properly on array, and cannot be nested in the previous version
There was a problem hiding this comment.
It's not just the array based lookups, there's also the non-existent key case (5th point in this PR description - apache/pinot#13139). I'm wondering how we can best phrase these differences in semantics? If we call out all the details with examples, it might end up being unnecessarily confusing to new users.
There was a problem hiding this comment.
The current one looks good. We may iterate on this if user asks for it
basics/indexing/json-index.md
Outdated
| @@ -419,6 +448,8 @@ FROM mytable | |||
| WHERE JSON_MATCH(person, '"$.name"=''adam'' AND "$.addresses[*].number"=112') | |||
| ``` | |||
|
|
|||
| `NOT IN` and `!=` can be used in nested filter expressions starting from Pinot 1.2.0. Note that `IS NULL` cannot be used in nested filter expressions currently. | |||
There was a problem hiding this comment.
NOT INand!=can be used in nested filter expressions starting from Pinot 1.2.0
I'm wondering if this needs to be stated explicitly or can be omitted?
There was a problem hiding this comment.
We can put them in a hint blob. We can phrase it as it was not supported before 1.2.0
Documentation for enhancements from: