You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but it’s very slow (even with small number of scanned documents (21). And I was thinking that maybe having it directly with JSON_MATCH could speed-up this operation?
JSON_MATCH("labels", 'demande_intention LIKE ''terminal''')
Is there a natural way for you to filter the JSON documents before applying the JSONEXTRACTSCALAR and REGEXP_LIKE functions? Without an index structured to support these functions, they are naturally quite expensive.
Have you considered extracting $.demande_intention into a text column during ingestion so you can create a text index on it, instead of storing it embedded in JSON?
~600-800ms for 21 documents (vs 22-40ms without this filter)
Is there a natural way for you to filter the JSON documents before applying the JSONEXTRACTSCALAR and REGEXP_LIKE functions? Without an index structured to support these functions, they are naturally quite expensive.
I'm using a JSON index on the column and operations like JSON_MATCH(labels, 'demande_intention = ''foo''') are fast (30-40ms)
Have you considered extracting $.demande_intention into a text column during ingestion so you can create a text index on it, instead of storing it embedded in JSON?
Yep I know it would be the best way to do it but since the labels column contains dynamic data, we don't want to add each field of the JSON object to the schema
Hello,
I was wondering if it was planned to add the LIKE operator to JSON_MATCH ? I’m currently using
but it’s very slow (even with small number of scanned documents (21). And I was thinking that maybe having it directly with JSON_MATCH could speed-up this operation?
edit: the
labels
column already have a JSON indexThank you
cc @atris
The text was updated successfully, but these errors were encountered: