[
https://issues.apache.org/jira/browse/FLINK-23424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384055#comment-17384055
]
Timo Walther commented on FLINK-23424:
--------------------------------------
This should not be an issue. All usages of
{{BatchExecutionUtils#applyBatchExecutionSettings}} are guarded by checking for
a state key selector or for specific {{Keyed}} transformations. Since the
planner does only insert partitioners in batch mode and is not using
transformations such as {{KeyedBroadcastStateTransformation,
KeyedMultipleInputTransformation, ReduceTransformation}}, we should be safe.
> Disable key sorting for Transformations created within table planner
> --------------------------------------------------------------------
>
> Key: FLINK-23424
> URL: https://issues.apache.org/jira/browse/FLINK-23424
> Project: Flink
> Issue Type: Sub-task
> Components: API / DataStream, Table SQL / API
> Reporter: Timo Walther
> Assignee: Timo Walther
> Priority: Major
>
> In batch mode, the table planner is fully in control of the generated
> Transformations. So we can disable the key sorting in this case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
