[
https://issues.apache.org/jira/browse/BEAM-11213?focusedWorklogId=561087&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-561087
]
ASF GitHub Bot logged work on BEAM-11213:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Mar/21 19:31
Start Date: 04/Mar/21 19:31
Worklog Time Spent: 10m
Work Description: iemejia edited a comment on pull request #14132:
URL: https://github.com/apache/beam/pull/14132#issuecomment-790871613
Thanks Kyle, actually that class is marked as `@DeveloperApi` that's the
Spark equivalent of Beam's `@Internal` so no guarantees. Also in Scala that
change makes more sense because of optional method parameters with default
values.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 561087)
Time Spent: 11h 10m (was: 11h)
> Beam metrics should be displayed in Spark UI
> --------------------------------------------
>
> Key: BEAM-11213
> URL: https://issues.apache.org/jira/browse/BEAM-11213
> Project: Beam
> Issue Type: Wish
> Components: runner-spark
> Reporter: Kyle Weaver
> Assignee: Tomasz Szerszen
> Priority: P2
> Labels: portability-spark
> Fix For: 2.29.0
>
> Time Spent: 11h 10m
> Remaining Estimate: 0h
>
> All Beam metrics are visible in the Spark UI in a single accumulator value
> (in the "Accumulators" tab), which is a large, hard-to-read blob. Originally,
> this blob was rendered in a bespoke format
> (https://github.com/apache/beam/blob/ead80b469ffeeddcd8e9e5c8dc462eec0b0ffc6b/sdks/java/core/src/main/java/org/apache/beam/sdk/metrics/MetricQueryResults.java#L63-L72).
> I changed the format to JSON so it could be easily deserialized (BEAM-9600).
> But then an issue was filed (BEAM-10294) reporting that the new JSON format
> was harder to read than the original bespoke format. The temporary fix was to
> revert to the bespoke format in Spark, while allowing Flink to continue to
> use JSON. However, if Beam metrics are only visible as an accumulator, then
> they are also unreadable because the payloads are in binary form (BEAM-10719).
> Having metrics visible in Spark's "Metrics" tab would A) make metrics easier
> to read (even compared to the bespoke accumulator string format), and closer
> to what users of Beamless Spark expect, and B) free us to use the accumulator
> however we wish for Beam internal purposes, without worrying about
> readability.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
