beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Wegner (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-767) Add DisplayData builder '.nested(..)' operation
Date Tue, 18 Oct 2016 16:10:58 GMT

     [ https://issues.apache.org/jira/browse/BEAM-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Scott Wegner updated BEAM-767:
------------------------------
    Description: 
See: https://github.com/apache/incubator-beam/pull/1088#discussion_r83332515

In the Java SDK, components can register display data directly, as well as include display
data from sub-components via the 'include(..)' operation. In [PR #1008|https://github.com/apache/incubator-beam/pull/1088],
we add 'paths' to display data metadata and also include a 'delegate(..)' action.

During the change for paths, we noticed an emerging pattern where components will typically
add the .getClass() of a subcomponent before including it. We can support this convention
better by embedding it in a single configurable operation, '.nested(..)'

  was:
See: https://github.com/apache/incubator-beam/pull/1088#discussion_r83332515

In the Java SDK, components can register display data directly, as well as include display
data from sub-components via the 'include(..)' operation. In [BEAM-1008|https://github.com/apache/incubator-beam/pull/1088],
we add 'paths' to display data metadata and also include a 'delegate(..)' action.

During the change for paths, we noticed an emerging pattern where components will typically
add the .getClass() of a subcomponent before including it. We can support this convention
better by embedding it in a single configurable operation, '.nested(..)'


> Add DisplayData builder '.nested(..)' operation
> -----------------------------------------------
>
>                 Key: BEAM-767
>                 URL: https://issues.apache.org/jira/browse/BEAM-767
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Scott Wegner
>            Assignee: Scott Wegner
>
> See: https://github.com/apache/incubator-beam/pull/1088#discussion_r83332515
> In the Java SDK, components can register display data directly, as well as include display
data from sub-components via the 'include(..)' operation. In [PR #1008|https://github.com/apache/incubator-beam/pull/1088],
we add 'paths' to display data metadata and also include a 'delegate(..)' action.
> During the change for paths, we noticed an emerging pattern where components will typically
add the .getClass() of a subcomponent before including it. We can support this convention
better by embedding it in a single configurable operation, '.nested(..)'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message