[
https://issues.apache.org/jira/browse/FLINK-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16973434#comment-16973434
]
Chesnay Schepler commented on FLINK-14740:
------------------------------------------
This has been discussed in the past; exposing the operator ID in the web UI
doesn't make sense if no sense if this ID isn't used anywhere else in the
runtime. You wouldn't be able to correlate an operator ID to a given task, be
it in the logs or from within your function.
Hence this requires a _much_ more holistic approach, that goes way beyond
metrics.
> Create OperatorID for OperatorMetricGroup which in batch job
> -------------------------------------------------------------
>
> Key: FLINK-14740
> URL: https://issues.apache.org/jira/browse/FLINK-14740
> Project: Flink
> Issue Type: Wish
> Components: Runtime / Metrics
> Reporter: lining
> Priority: Major
>
> Now OperatorMetricGroup which in batch job use VertexId as OperatorId. For
> chain operator, they'll use the same id, if two chain operators which have
> same name. I We could update in JobGraphGenerator.compileJobGraph
> {code:java}
> for (TaskInChain tic : this.chainedTasksInSequence) {
> TaskConfig t = new
> TaskConfig(tic.getContainingVertex().getConfiguration());
> Integer nodeId = tic.getPlanNode().getOptimizerNode().getId();
> OperatorID operatorID = this.nodeId2OperatorId.get(nodeId);
> if(operatorID == null) {
> operatorID = new OperatorID();
> this.nodeId2OperatorId.put(nodeId, operatorID);
> }
> t.addChainedTask(tic.getChainedTask(), tic.getTaskConfig(),
> tic.getTaskName(), operatorID.toString());
> }
> {code}
> Then we could get id from TaskInfo.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
