[
https://issues.apache.org/jira/browse/FLINK-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16424315#comment-16424315
]
ASF GitHub Bot commented on FLINK-5480:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/3117
@ShashwatRastogi-Reflektion I'm not entirely sure, but one thing you could
try is to explicitly disable chaining
(`StreamExecutionEnvironment#disableOperatorChaining`). This way the ID of each
operator (that now runs as a separate task) should be logged / be visible in
the UI.
> User-provided hashes for operators
> ----------------------------------
>
> Key: FLINK-5480
> URL: https://issues.apache.org/jira/browse/FLINK-5480
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API
> Affects Versions: 1.2.0
> Reporter: Stefan Richter
> Assignee: Stefan Richter
> Priority: Major
> Fix For: 1.2.0, 1.3.0
>
>
> We could allow users to provided (alternative) hashes for operators in a
> StreamGraph. This can make migration between Flink versions easier, in case
> the automatically produced hashes between versions are incompatible. For
> example, users could just copy the old hashes from the web ui to their job.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
