[jira] [Resolved] (TEZ-182) Can I has API to attach configuration to Vertices and Edges?

["Siddharth Seth (JIRA)" <ji...@apache.org>]

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

Siddharth Seth resolved TEZ-182.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.2.0

Resolving since the sub-tasks have been committed.

Note: The input/output payloads are currently not used. They can be set, but will be ignored. This works for now since there is no differentiation in the existing MR runtime. Would suggest not setting them though - since that will only add to the size of the data being localized per task.
                
> Can I has API to attach configuration to Vertices and Edges?
> ------------------------------------------------------------
>
>                 Key: TEZ-182
>                 URL: https://issues.apache.org/jira/browse/TEZ-182
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Gunther Hagleitner
>            Assignee: Siddharth Seth
>              Labels: TEZ-0.2.0, TEZ-1
>             Fix For: 0.2.0
>
>         Attachments: TEZ-182.2.txt, TEZ-182_outline.txt
>
>
> Hive as well as other Apps are going to have to ship configuration to the actual Processors.
> The requested API would let you attach (static) data to each vertex and edge  as well as the DAG itself at the time the DAG is assembled. The expectation is that the Processor has a structured way to retrieve that data for itself (the vertex) any edge connected to it as well as the overall "DAG" config.
> The shape of the configuration could be anything. At a minimum having a byte buffer would be sufficient (up to the app what serialization to use for the config).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira