[
https://issues.apache.org/jira/browse/CALCITE-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753253#comment-16753253
]
xuqianjin edited comment on CALCITE-2791 at 1/27/19 3:19 AM:
-------------------------------------------------------------
hi [~zhztheplayer] Thank you very much for your suggestion. The reason why I
want to extend the json function is that flink does not support dialect
functions like mysql. I want to add a list of available json functions to
calcite against the mysql json function. Because I'm not familiar with json, I
saw your implementation do some work on its own. Please correct me if there is
anything wrong. Thanks again.
best
qianjin
was (Author: x1q1j1):
hi [~zhztheplayer] Thank you very much for your suggestion. The reason why I
want to extend the json function is that flink does not support dialect
functions like mysql. I want to add a list of available json functions to
calcite against the mysql json function. Because I'm not familiar with json, I
saw your implementation do some work on its own.
best
qianjin
> Add the JSON_TYPE function
> --------------------------
>
> Key: CALCITE-2791
> URL: https://issues.apache.org/jira/browse/CALCITE-2791
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: xuqianjin
> Assignee: Julian Hyde
> Priority: Major
> Labels: https://github.com/apache/calcite/pull/1013
>
> The data in json can be =, <, <=, >, >=, <>,! =, and <=>. But the data types
> in json can be diverse, so when you compare different types, you have a
> priority, and the high priority is greater than the low priority (you can
> view the types with the JSON_TYPE() function). The priorities are as follows:
> BOOLEAN
> ARRAY
> OBJECT
> STRING
> INTEGER
> LONG
> DOUBLE
> NULL
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
