[
https://issues.apache.org/jira/browse/PIG-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Kamath updated PIG-269:
-------------------------------
Attachment: hadoop17.patch
Patch which addresses the following JIRAs with caveats listed below:
PIG-250: speculative execution is broken;
PIG-198: Integration with hadoop 17
Caveats:
Files not patched:
src/org/apache/pig/backend/executionengine/PigSlicer.java - not present yet in
types
src/org/apache/pig/backend/hadoop/executionengine/HExecutionEngine.java -
changes depend on Config properties change
src/org/apache/pig/backend/hadoop/executionengine/mapreduceExec/PigMapReduce.java
- this is present in ../impl/mapReduceLayer now and is different in content -
depends on some other change going in first which will cause PigMapReduce to
"implement" MapRunnable and Reducer (in the types branch it currently does not
implement any interface)
src/org/apache/pig/backend/hadoop/executionengine/mapreduceExec/PigCombine.java
- not present in types
This patch also includes changes to build.xml (besides the change for hadoop17)
to:
1) show deprecation warnings in default compiles
2) support to show all compilation warnings if "-Dall.warnings=1" is supplied
on cmdline
Before applying the patch, hadoop17.jar should be copied to the lib
subdirectory. I couldn't figure a way to upload that as part of the patch (is
that even possible?)
The 3 unit tests - TestEvalPipeline, TestFilterOpNumeric and TestStoreOld still
fail after application of this patch but are unrelated to its contents.
> Merge changes from trunk to "types" branch
> ------------------------------------------
>
> Key: PIG-269
> URL: https://issues.apache.org/jira/browse/PIG-269
> Project: Pig
> Issue Type: Sub-task
> Reporter: Pradeep Kamath
> Assignee: Alan Gates
> Attachments: hadoop17.patch, merge_main_to_types_batch1.patch,
> PIG-256.patch
>
>
> A lot of changes have gone into trunk since the "types" branch was created.
> This jira issue is to track merging the changes from trunk to "types" branch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
