[ https://issues.apache.org/jira/browse/CALCITE-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771610#comment-16771610 ]
Forward Xu commented on CALCITE-2791: ------------------------------------- hi [~zhztheplayer] Thank you very much. I had to add the Jira test case below. {code:java} // code placeholder CalciteAssert.that() .query("SELECT JSON_TYPE(v) AS c1\n" + ",JSON_TYPE(JSON_VALUE(v, 'lax $.b' ERROR ON ERROR)) AS c2\n" + ",JSON_TYPE(JSON_VALUE(v, 'strict $.a[0]' ERROR ON ERROR)) AS c3\n" + ",JSON_TYPE(JSON_VALUE(v, 'strict $.a[1]' ERROR ON ERROR)) AS c4\n" + "FROM (VALUES ('{\"a\": [10, true],\"b\": \"[10, true]\"}')) AS t(v)\n" + "limit 10") .returns("C1=OBJECT; C2=ARRAY; C3=INTEGER; C4=BOOLEAN\n"); {code} 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: Forward Xu > Assignee: Julian Hyde > Priority: Major > Labels: pull-request-available > Attachments: image-2019-02-19-12-24-10-200.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > 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,INTEGE,DOUBLE,NULL > Example Data: > {"a":[10,true]} > SELECT JSON_TYPE(v) AS c1, > JSON_TYPE(a) AS c2, > JSON_TYPE(b) AS c3, > JSON_TYPE(c) AS c4 FROM (VALUES ('\{"a": [10, true]}','[10, true]', '10', > 'true')) AS t(v, a, b, c) > limit 10; > c1 c2 c3 c4 > ======= ======= ======= ======= > OBJECT ARRAY INTEGER BOOLEAN -- This message was sent by Atlassian JIRA (v7.6.3#76005)