Thanks Danny!
On Tue, 21 Apr 2020 at 16:24, Danny Chan wrote:
> The JSON_VALUE was coded into the parser, which is always parsed as the
> builtin operator, so there is no change to override it yet.
>
> I have fired an issue[1] to track this and hope we can resolve it in the
> next Calcite
The JSON_VALUE was coded into the parser, which is always parsed as the builtin
operator, so there is no change to override it yet.
I have fired an issue[1] to track this and hope we can resolve it in the next
Calcite release.
[1] https://issues.apache.org/jira/browse/CALCITE-3943
Best,
Danny
; danny0...@apache.org>
> *抄送:* seeksst; user; Timo Walther<
> twal...@apache.org>
> *发送时间:* 2020年4月17日(周五) 22:53
> *主题:* Re: Flink upgrade to 1.10: function
>
> Hi,
>
> I guess you are already close to the truth. Since Flink 1.10 we upgraded
> Calcite to 1.21 wh
: Flink upgrade to 1.10: function
Hi,
I guess you are already close to the truth. Since Flink 1.10 we upgraded
Calcite to 1.21 which reserves JSON_VALUE as keyword.
So that a user define function can't use this name anymore. That's why
JSON_VALUE(...) will always be parsed as the Calcite's
Hi,
I guess you are already close to the truth. Since Flink 1.10 we upgraded
Calcite to 1.21 which reserves JSON_VALUE as keyword.
So that a user define function can't use this name anymore. That's why
JSON_VALUE(...) will always be parsed as the Calcite's builtin function
definition.
Currently,
Hi,
thanks for reporting these problems. I'm pulling in Timo and Jark who are
working on the SQL component. They might be able to help you with your
problem.
Cheers,
Till
On Thu, Apr 16, 2020 at 11:10 AM seeksst wrote:
> Hi, All
>
>
> Recently, I try to upgrade flink from 1.8.2 to 1.10, but i
Hi, All
Recently, I try to upgrade flink from 1.8.2 to 1.10, but i meet some problem
about function. In 1.8.2, there are just Built-In function and User-defined
Functions, but in 1.10, there are 4 categories of funtions.
I defined a function which named JSON_VALUE in my system, it doesn’t
