[
https://issues.apache.org/jira/browse/FLINK-31066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693275#comment-17693275
]
Matthias Pohl commented on FLINK-31066:
---------------------------------------
I should have remembered that the backwards compatibility between minor Flink
version with changed execution plan is not given
[[1]|https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/concepts/overview/#stateful-upgrades-and-evolution]
[[2]|https://nightlies.apache.org/flink/flink-docs-master/docs/ops/upgrading/#table-api--sql].
🤦♂️ So, I guess, there's no point of checking this. [~Sergey Nuyanzin] do you
consider it good enough to prove that the calcite update could be visualized
through the Flink UI?
> Release Testing: Verify FLINK-29932 Upgrade Calcite to 1.29.0
> -------------------------------------------------------------
>
> Key: FLINK-31066
> URL: https://issues.apache.org/jira/browse/FLINK-31066
> Project: Flink
> Issue Type: Sub-task
> Components: Tests
> Reporter: Sergey Nuyanzin
> Assignee: Matthias Pohl
> Priority: Major
> Labels: release-testing
> Attachments: SavepointReleaseTesting.java
>
>
> In fact this is a task to check all 3 Calcite upgrade related issues (1.27.0,
> 1.28.0 and 1.29.0)
> Since there were added optimization for Sarg in Calcite 1.27.0 it would make
> sense to check that different queries with Sarg operator are working ok.
> Also would make sense to check that SQL jobs with Sarg related queries could
> be restored from previous Flink version.
> An example of SQL
> {code:sql}
> SELECT a FROM MyTable WHERE a = 1 or a = 2 or a IS NOT NULL;{code}
> {code:sql}
> SELECT a FROM MyTable WHERE a = 1 or a = 2 or a IS NULL;
> {code}
> where MyTable is for instance
> {code:sql}
> CREATE TABLE MyTable (
> a bigint,
> b int not null,
> c varchar,
> d timestamp(3)
> ) with (...)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
