You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Gunther Hagleitner (JIRA)" <ji...@apache.org> on 2013/07/09 02:13:49 UTC

[jira] [Updated] (HIVE-4825) Separate MapredWork into MapWork and ReduceWork

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

Gunther Hagleitner updated HIVE-4825:
-------------------------------------

    Attachment: HIVE-4825.1.patch
    
> Separate MapredWork into MapWork and ReduceWork
> -----------------------------------------------
>
>                 Key: HIVE-4825
>                 URL: https://issues.apache.org/jira/browse/HIVE-4825
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Gunther Hagleitner
>            Assignee: Gunther Hagleitner
>         Attachments: HIVE-4825.1.patch
>
>
> Right now all the information needed to run an MR job is captured in MapredWork. This class has aliases, tagging info, table descriptors etc.
> For Tez and MRR it will be useful to break this into map and reduce specific pieces. The separation is natural and I think has value in itself, it makes the code easier to understand. However, it will also allow us to reuse these abstractions in Tez where you'll have a graph of these instead of just 1M and 0-1R.

--
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