[
https://issues.apache.org/jira/browse/PIG-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740339#action_12740339
]
Dmitriy V. Ryaboy commented on PIG-660:
---------------------------------------
Nate,
Your stacktrace shows hadoop.dfs calls (as opposed to hdfs) which tells me it's
looking for -- and finding -- hadoop 18 classes.
Can you do this:
export PIG_HADOOP_VERSION=20
ant clean; ant -Dhadoop.version=20
any try again?
Just to be sure, try moving hadoop1* out of the lib directory (so that it for
sure fails if it's trying to look for 18).
> Integration with Hadoop 0.20
> ----------------------------
>
> Key: PIG-660
> URL: https://issues.apache.org/jira/browse/PIG-660
> Project: Pig
> Issue Type: Bug
> Components: impl
> Affects Versions: 0.2.0
> Environment: Hadoop 0.20
> Reporter: Santhosh Srinivasan
> Assignee: Santhosh Srinivasan
> Fix For: 0.4.0
>
> Attachments: PIG-660-for-branch-0.3.patch, PIG-660.patch,
> PIG-660_1.patch, PIG-660_2.patch, PIG-660_3.patch, PIG-660_4.patch,
> PIG-660_5.patch, pig_660_shims.patch, pig_660_shims_2.patch,
> pig_660_shims_3.patch
>
>
> With Hadoop 0.20, it will be possible to query the status of each map and
> reduce in a map reduce job. This will allow better error reporting. Some of
> the other items that could be on Hadoop's feature requests/bugs are
> documented here for tracking.
> 1. Hadoop should return objects instead of strings when exceptions are thrown
> 2. The JobControl should handle all exceptions and report them appropriately.
> For example, when the JobControl fails to launch jobs, it should handle
> exceptions appropriately and should support APIs that query this state, i.e.,
> failure to launch jobs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
