hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunther Hagleitner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-4825) Separate MapredWork into MapWork and ReduceWork
Date Mon, 15 Jul 2013 06:04:48 GMT

    [ https://issues.apache.org/jira/browse/HIVE-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708256#comment-13708256
] 

Gunther Hagleitner commented on HIVE-4825:
------------------------------------------

Ran tests on 1 & 2 line. Came back clean. Split in code + test, because there's lots of
whitespace only diffs. I've also updated the review.
                
> 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, HIVE-4825.2.code.patch, HIVE-4825.2.testfiles.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

Mime
View raw message