[
https://issues.apache.org/jira/browse/FLINK-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915595#comment-16915595
]
Jark Wu commented on FLINK-13547:
---------------------------------
Hi [~KevinZwx], the removed function can be definitely introduced in 1.10 with
a more standard way. They are removed because of unreasonable function name or
arguments or need more discussion about the behavior. We don't have enough time
to have all of them in 1.10. In order to have a better compatibility, we
removed them in 1.9.
Regarding to the jsonvalue function, I agree it is an important function, and
we should support it in 1.10 (FLINK-9477). If you are interested, you can help
and contribute it.
> 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)
