You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2013/06/07 07:52:22 UTC

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

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

Siddharth Seth updated TEZ-182:
-------------------------------

    Attachment: TEZ-182_outline.txt

Initial patch - in case anyone has feedback.

Will change the Configuration object to a byte buffer later on. Not very friendly, but is useful if a processor chooses to use something other than hadoop-configuration, or wants to move additional data over to tasks (e.g. splits, an execution plan, configuration other than Hadoop conf and so on).

Other stuff pending - javadoc, actual serialization, runtime changes (likely a separate jira), etc
                
> 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
>         Attachments: 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