[
https://issues.apache.org/jira/browse/FLINK-31362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817717#comment-17817717
]
Sergey Nuyanzin edited comment on FLINK-31362 at 2/15/24 3:51 PM:
------------------------------------------------------------------
Calcite upgrade itself is pretty complex task that's why it was already
discussed and suggested to go version by version rather than big bang
https://issues.apache.org/jira/browse/FLINK-27998?focusedCommentId=17597797&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17597797
this is the main concern
I fear we can not just downgrade it easily, there is already functionality
merged which depends on Calcite 1.31.0 e.g. FLINK-24024
Also upgrade brought a number of fixes/improvements which will be rollbacked
together with downgrade.
Plans and parser behavior will be changed again, which means it is definitely a
no go for minor version
Let's first see how big is the current issue and what we can do about it
I can have a look closer to it in coming days
was (Author: sergey nuyanzin):
Calcite upgrade itself is pretty complex task that's why it was already
discussed and suggested to go version by version rather than big bang
https://issues.apache.org/jira/browse/FLINK-27998?focusedCommentId=17597797&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17597797
this is the main concern
I fear we can not just downgrade it easily, there is already functionality
merged which depends on Calcite 1.31.0 e.g. FLINK-24024
Let's first see how big is the current issue and what we can do about it
I can have a look closer to it in coming days
> Upgrade to Calcite version to 1.33.0
> ------------------------------------
>
> Key: FLINK-31362
> URL: https://issues.apache.org/jira/browse/FLINK-31362
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: WenJun Min
> Assignee: Sergey Nuyanzin
> Priority: Major
> Labels: pull-request-available
>
> In Calcite 1.33.0, C-style escape strings have been supported. We could
> leverage it to enhance our string literals usage.
> issue: https://issues.apache.org/jira/browse/CALCITE-5305
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
