[
https://issues.apache.org/jira/browse/FLINK-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915538#comment-16915538
]
Zhenghua Gao commented on FLINK-13547:
--------------------------------------
[~KevinZwx] There is no substitute JSON functions now. And a Jira ticket has
been created for SQL:2016 json functions
[FLINK-9477|https://issues.apache.org/jira/browse/FLINK-9477]
> Verify and correct string function's semantic for Blink planner
> ---------------------------------------------------------------
>
> Key: FLINK-13547
> URL: https://issues.apache.org/jira/browse/FLINK-13547
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Zhenghua Gao
> Assignee: Zhenghua Gao
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently many string builtin functions in blink planner follow hive/spark
> semantics, which should keep compatible with old planner. And some
> non-standard functions(Blink planner intros) should be removed.
> * concat/concat_ws function (null treatment)
> * substring function (follow calcite/flink)
> * from_base64 should return string not binary
> * intro truncate function to blink planner
> * uuid should be no-argument (remove the one-argument version)
> * length/jsonvalue/keyvalue/substr (non-standard function should be removed)
> * md5/sha1/sha2/sha224/sha256/sha384/sha512(remove the two-arguments version)
> * ascii (operand type should beSqlTypeFamily.CHARACTER)
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
