Dmitriy V. Ryaboy commented on PIG-660:

The shim patch posted above doesn't work as cleanly as desired; the current 
build.xml has junit.hadoop.conf points to a directory in ${user.home}

This has an undesired effect -- a hadoop config file gets created the first 
time you run ant, which among other things sets what class implements the 
FileSytem interface. When ant gets re-run with a different hadoop version, 'ant 
clean' does not clean out this file -- so an incorrect fs class name gets used. 
 Deleting the directory created by junit.hadoop.conf before rerunning fixes the 
problem; so does putting the value of junit.hadoop.conf relative to 
${build.dir} instead of ${user.home}.  

As I am not sure how the Y! developers use their pigconf directories this thing 
references, I do not know the appropriate way to proceed. Comments?

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

Reply via email to