[
https://issues.apache.org/jira/browse/GOBBLIN-1217?focusedWorklogId=461706&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-461706
]
ASF GitHub Bot logged work on GOBBLIN-1217:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Jul/20 18:26
Start Date: 21/Jul/20 18:26
Worklog Time Spent: 10m
Work Description: arjun4084346 commented on a change in pull request
#3065:
URL: https://github.com/apache/incubator-gobblin/pull/3065#discussion_r458302607
##########
File path:
gobblin-metrics-libs/gobblin-metrics/src/main/java/org/apache/gobblin/metrics/GobblinMetrics.java
##########
@@ -367,6 +374,20 @@ public void startMetricReportingWithFileSuffix(State
state, String metricsFileSu
oldMetricsFileSuffix += "." + metricsFileSuffix;
}
metricsReportingProps.setProperty(ConfigurationKeys.METRICS_FILE_SUFFIX,
oldMetricsFileSuffix);
+
+ if (!Strings.isNullOrEmpty(metricsFileSuffix)) {
+ String[] tokens = metricsFileSuffix.split("_");
Review comment:
I could not find any API which gives task number and attempt.
getTaskAttemptID().getJobID(), getTaskAttemptID().getTaskID(),
getTaskAttemptID().getId() did not quite give what I am trying to extract from
taskAttemptID.
I'll use context.getTaskAttemptID().getTaskType()
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 461706)
Time Spent: 50m (was: 40m)
> add a few map/reduce task related configs in building metric reporter
> ---------------------------------------------------------------------
>
> Key: GOBBLIN-1217
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1217
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Arjun Singh Bora
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> one of the use case can be that each mapper/reducer's metrics can be analyzed
> separately
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
