[
https://issues.apache.org/jira/browse/CALCITE-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833246#comment-16833246
]
Hongze Zhang commented on CALCITE-3010:
---------------------------------------
Removed in a follow up commit
[0d504d|https://github.com/apache/calcite/commit/0d504d20d47542e8d461982512ae0e7a94e4d6cb].
So sorry for the mistake.
> In SQL parser, move JsonValueExpression into Expression
> -------------------------------------------------------
>
> Key: CALCITE-3010
> URL: https://issues.apache.org/jira/browse/CALCITE-3010
> Project: Calcite
> Issue Type: Sub-task
> Reporter: Hongze Zhang
> Assignee: Hongze Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.20.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Below is the syntax definition of {{JsonValueExpression}} from ISO/SEC
> 19075-6:
> {code:java}
> <JSON value expression> ::=
> <value expression> [ <JSON input clause> ]
> <JSON input clause> ::=
> FORMAT <JSON representation>
> <JSON representation> ::=
> JSON [ ENCODING { UTF8 | UTF16 | UTF32 } ]
> | <implementation-defined JSON representation option>
> {code}
> Currently it's an individual syntax standing out of {{Expression}} for easily
> implementing the behavior of "implicit JSON format". As the amount of JSON
> functions is getting larger, the design could definitely be improved. For
> example, it can be categorized as a PostfixOperator[1].
> [1]
> [https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/sql/SqlPostfixOperator.java]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
