This topic describes how the compatibility between a deployment and the state data is affected when you perform different modifications in SQL statements for the deployment.
To check the compatibility between a deployment and the state data after modification, you can view the state compatibility check result in the Start Job panel of the Deployments page in the development console of Realtime Compute for Apache Flink.
Scenario | Description | References |
Modify a query | Describes how the compatibility between a deployment and the state data is affected after you change an alias in an SQL statement for the deployment. If you change an alias, the compatibility between the deployment and the state data is not affected. | |
Describes how the compatibility between a deployment and the state data is affected after you modify an aggregate function that is used with GROUP BY in an SQL statement for the deployment. | ||
Describes how the compatibility between a deployment and the state data is affected after you modify an aggregate function that is used with OVER in an SQL statement for the deployment. | ||
Describes how the compatibility between a deployment and the state data is affected after you modify a window aggregate function that is used with GROUP BY in an SQL statement for the deployment. | ||
Describes how the compatibility between a deployment and the state data is affected after you modify a window table-valued function (TVF) in an SQL statement for the deployment. | ||
Describes how the compatibility between a deployment and the state data is affected after you modify deduplication in an SQL statement for the deployment. | ||
Describes how the compatibility between a deployment and the state data is affected after you modify a TopN function in an SQL statement for the deployment. | ||
Describes how the compatibility between a deployment and the state data is affected after you modify a window-based TopN function in an SQL statement for the deployment. | ||
Describes how the compatibility between a deployment and the state data is affected after you modify a regular join, interval join, temporal join, or lookup join in an SQL statement for the deployment. | ||
Describes how the compatibility between a deployment and the state data is affected after you modify pattern recognition in an SQL statement for the deployment. | ||
Describes how the compatibility between a deployment and the state data is affected after you modify the WHERE clause in an SQL statement for the deployment. | ||
Describes how the compatibility between a deployment and the state data is affected after you modify UNION ALL in an SQL statement for the deployment. | ||
Describes how the compatibility between a deployment and the state data is affected after you modify the temporal sorting in an SQL statement for the deployment. | ||
Describes how the compatibility between a deployment and the state data is affected after you modify the LIMIT clause in an SQL statement for the deployment. | ||
Modify the source connector | Describes how the compatibility between a deployment and the state data is affected after you modify the source connector in an SQL statement for the deployment. | |
Modify a sink connector | Describes how the compatibility between a deployment and the state data is affected after you modify a sink connector in an SQL statement for the deployment. | |
Other limits | Describes the limits that apply when you modify SQL statements for a deployment, excluding the query, source connector, and sink connector of the deployment. |
The table that is created by using the following DDL statement is used as the source table for the sample SQL statements in the preceding scenarios.
CREATE TEMPORARY TABLE MyTable (
a int,
b bigint,
c varchar,
d int,
ts timestamp(3),
proctime as proctime(),
watermark for ts AS ts - interval '1' second
) WITH (
...);