[
https://issues.apache.org/jira/browse/FLINK-31679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707526#comment-17707526
]
Weijie Guo commented on FLINK-31679:
------------------------------------
{code:java}
My option is that the consuming behavior of data exchange can be described by
the ConsumingConstraint enum in ResultPartitionType.java.
{code}
[~Wencong Liu] I'm not sure if exposing it to users will cause trouble to them,
after all, this is still only a concept inside the framework. After we unify
the implementation of shuffle service, it becomes more meaningful for the
scheduler to judge the scheduling constraints between upstream and downstream,
and then expose them to user. At least at this stage, users are more aware of
the specific types of shuffle like Blocking/Pipelined/Hybrid. WDYT
> [Flink][UI] Show data exchange type on web ui
> ---------------------------------------------
>
> Key: FLINK-31679
> URL: https://issues.apache.org/jira/browse/FLINK-31679
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Affects Versions: 1.18.0
> Reporter: Weihua Hu
> Priority: Major
>
> Flink supports multiple data exchange types (ResultPartitionType), which
> subject to multiple parameters, such as whether job is streaming or batch.
> I think display the data exchange types on the UI would be helpful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
