You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Valentyn Tymofieiev (Jira)" <ji...@apache.org> on 2019/10/24 22:12:00 UTC
[jira] [Commented] (BEAM-366) Support Display Data on Composite
Transforms
[ https://issues.apache.org/jira/browse/BEAM-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16959262#comment-16959262 ]
Valentyn Tymofieiev commented on BEAM-366:
------------------------------------------
[~joar], very likely. I encountered this issue recently while debugging a failure in test_remote_runner_display_data: https://issues.apache.org/jira/browse/BEAM-8397.
> Support Display Data on Composite Transforms
> --------------------------------------------
>
> Key: BEAM-366
> URL: https://issues.apache.org/jira/browse/BEAM-366
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: Ben Chambers
> Priority: Major
>
> Today, the Dataflow runner doesn't represent composites all the way to the UI (it reconstructs them from the name). This means it doesn't support attaching Display Data to composites.
> With the runner API refactoring, Dataflow runner should start supporting composites, at which point we should make sure that Display Data is plumbed through properly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)