[
https://issues.apache.org/jira/browse/FLINK-37134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Li updated FLINK-37134:
----------------------------
Attachment: image-2025-02-27-20-04-02-689.png
> Cross-team verification for FLIP-492
> ------------------------------------
>
> Key: FLINK-37134
> URL: https://issues.apache.org/jira/browse/FLINK-37134
> Project: Flink
> Issue Type: Sub-task
> Reporter: Feng Jin
> Assignee: Yang Li
> Priority: Major
> Fix For: 2.0.0
>
> Attachments: image-2025-02-27-20-03-38-176.png,
> image-2025-02-27-20-03-50-430.png, image-2025-02-27-20-04-02-689.png,
> image-2025-02-27-20-04-16-841.png, image-2025-02-27-20-04-31-211.png
>
>
> This is for cross-team verification of the release 2.0 work item:
> [https://cwiki.apache.org/confluence/display/FLINK/FLIP-492%3A+Support+Query+Modifications+for+Materialized+Tables]
> As only the Alter Query capability has been achieved at present, we only need
> to verify https://issues.apache.org/jira/browse/FLINK-36994.
>
> *Operation steps：*
> 1. Refer to
> quickstart(https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/materialized-table/quickstart/)
> to prepare the environment required for Materialized table: including
> catalog store/test-filesystem plugin/standalone cluster/sql gateway.
> 2. Create Materialized Tables in two modes (Continuous and Full).
> 3. Modify the As query of Materialized Tables in two modes.
>
> *Verify The result：*
> In Full mode, we need to verify the behavior of partitioned and
> non-partitioned tables:
> 1. For non-partitioned tablesafter waiting for the next refresh task to be
> completed, verify whether the result after modifying the query meets
> expectations.
> 2. For partitioned tables, we need to verify that only the result of the
> latest partition is consistent with the result after modifying the query, and
> the historical partitions remain unchanged. Then, by manually refreshing,
> confirm again that the partition after refreshing is generated by the
> modified query.
>
> In Continuous mode, we need to verify the execution of the background
> Continuous job after modification.
> 1. After modifying the as query, the new job is generated by the new query.
> 2. The new job does not resume from the state of historical jobs.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
