[
https://issues.apache.org/jira/browse/FLINK-31679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707512#comment-17707512
]
Wencong Liu commented on FLINK-31679:
-------------------------------------
Thanks [~huwh] for proposing this ticket. It is meaningful to display the
actual ResultPartitionType used for connecting upstream and downstream
operators on the Web UI. However, there are currently many types of
ResultPartitionType, and exposing specific names to users would make it
difficult for them to understand related behaviors.
My option is that the consuming behavior of data exchange can be described by
the ConsumingConstraint enum in ResultPartitionType.java :
{code:java}
private enum ConsumingConstraint {
/** Upstream must be finished before downstream consume. */
BLOCKING,
/** Downstream can consume while upstream is running. */
CAN_BE_PIPELINED,
/** Downstream must consume while upstream is running. */
MUST_BE_PIPELINED
} {code}
Perhaps displaying BLOCKING/CAN_BE_PIPELINED/MUST_BE_PIPELINED rather than the
ResultPartitionType on the web UI would be more friendly for users to
understand and devs to troubleshoot bugs. It would also decouple it from many
ResultPartitionTypes.
Of course, these all require further discussion:). cc [~Weijie Guo] [~xtsong]
> [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)
