You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Forward Xu (JIRA)" <ji...@apache.org> on 2019/03/01 03:43:00 UTC

[jira] [Resolved] (CALCITE-2791) Add the JSON_TYPE function

     [ https://issues.apache.org/jira/browse/CALCITE-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Forward Xu resolved CALCITE-2791.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.19.0

> Add the JSON_TYPE function
> --------------------------
>
>                 Key: CALCITE-2791
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2791
>             Project: Calcite
>          Issue Type: Sub-task
>          Components: core
>            Reporter: Forward Xu
>            Assignee: Forward Xu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.19.0
>
>         Attachments: image-2019-02-19-12-24-10-200.png
>
>          Time Spent: 3h 20m
>  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 Sql::
> {"a":[10,true]}
> SELECT JSON_TYPE(v) AS c1
>  ,JSON_TYPE(JSON_VALUE(v, 'lax $.b' ERROR ON ERROR)) AS c2
>  ,JSON_TYPE(JSON_VALUE(v, 'strict $.a[0]' ERROR ON ERROR)) AS c3
>  ,JSON_TYPE(JSON_VALUE(v, 'strict $.a[1]' ERROR ON ERROR)) AS c4
>  FROM (VALUES ('{"a": [10, true],"b": "[10, true]"}')) AS t(v)
>  limit 10;
> Result:
> c1 c2 c3 c4
>  ======= ======= ======= =======
>  OBJECT ARRAY INTEGER BOOLEAN



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)