Hello,
Calcite is used as the parsing layer of a database I am working on. I
noticed that calcite support dot notation and array subscripts in
identifiers as in:
SELECT json_column.person.name.email[5] FROM table
This allows for writing rudimentary Json Path expressions. However, some
suppor
If we add native JSON syntax to SQL, it is very likely that there will
be ambiguities. I think our best path for JSON support is to follow
the SQL standard (and perhaps some extensions made by other major
DBs), which consists of a set of functions to handle JSON. Quite a few
of those functions acce
Just to clarify that Calcite does not explicitly attempt to provide
any JSONPath support. The examples that you show just happen to work
based on standard SQL syntax.
--
Michael Mior
mm...@apache.org
Le lun. 3 mai 2021 à 14:25, Amrish Lal a écrit :
>
> Hello,
>
> Calcite is used as the parsing la
>
> You could try creating a variant of Calcite's SQL parser that accepts
> a wider syntax for expressions and desugars to the standard JSON_xxx
> functions.
Thanks, I will try it out and see if it works.
Although in my case, we would need to desugar to our
own non-standard JSON functions.
If th
