hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-4825) Separate MapredWork into MapWork and ReduceWork
Date Tue, 23 Jul 2013 18:02:49 GMT


Hive QA commented on HIVE-4825:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 2647 tests executed
*Failed tests:*

Test results:
Console output:

Executing org.apache.hive.ptest.execution.CleanupPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests failed with: TestsFailedException: 1 tests failed

This message is automatically generated.
> Separate MapredWork into MapWork and ReduceWork
> -----------------------------------------------
>                 Key: HIVE-4825
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Gunther Hagleitner
>            Assignee: Gunther Hagleitner
>            Priority: Minor
>         Attachments: HIVE-4825.1.patch, HIVE-4825.2.code.patch, HIVE-4825.2.testfiles.patch,
HIVE-4825.3.testfiles.patch, HIVE-4825.4.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:

View raw message