[
https://issues.apache.org/jira/browse/FLINK-40449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-40449:
-----------------------------------
Labels: pull-request-available (was: )
> Reject non-temporal streaming sort during planning instead of at job
> submission
> -------------------------------------------------------------------------------
>
> Key: FLINK-40449
> URL: https://issues.apache.org/jira/browse/FLINK-40449
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Reporter: Martijn Visser
> Priority: Major
> Labels: pull-request-available
>
> A streaming query that sorts on a non-time attribute (e.g. SELECT a FROM t
> ORDER BY c, where c is not an ascending time attribute) is not supported.
> Today the rejection is thrown during execution-plan translation, not during
> optimization.
> Consequences:
> * COMPILE PLAN FOR '<such a query>' succeeds and serializes a StreamExecSort
> that only fails later, at job (re)submission.
> * In SQL-gateway / REST flows the statement can enter a restart loop before
> the deterministic planning error is reported back to the user.
> The check is streaming-specific, but it is currently applied at the shared
> exec-node
> translation stage rather than where streaming diverges from batch.
> Proposal: reject the sort in the streaming physical conversion rule during
> the physical optimization phase, so the error is raised during
> optimize()/compilePlan, before job submission.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
