[
https://issues.apache.org/jira/browse/HCATALOG-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454149#comment-13454149
]
Rohini Palaniswamy commented on HCATALOG-499:
---------------------------------------------
The stacktrace encountered for the script in comment 1.
{code}
Caused by: java.io.FileNotFoundException: File
hdfs://gsbl90897.blue.ygrid.yahoo.com:8020/user/rohinip/testdb/table1/part=2/_temporary/1
does not exist.
at
org.apache.hadoop.hdfs.DistributedFileSystem.listStatus(DistributedFileSystem.java:362)
at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1355)
at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1395)
at
org.apache.hadoop.mapreduce.lib.output.FileOutputCommitter.getAllCommittedTaskPaths(FileOutputCommitter.java:262)
at
org.apache.hadoop.mapreduce.lib.output.FileOutputCommitter.commitJob(FileOutputCommitter.java:302)
at
org.apache.hadoop.mapred.FileOutputCommitter.commitJob(FileOutputCommitter.java:136)
at
org.apache.hadoop.mapred.OutputCommitter.commitJob(OutputCommitter.java:208)
at
org.apache.hcatalog.mapreduce.FileOutputCommitterContainer.commitJob(FileOutputCommitterContainer.java:163)
... 20 more
{code}
> Multiple store commands does not work with Hadoop23
> ---------------------------------------------------
>
> Key: HCATALOG-499
> URL: https://issues.apache.org/jira/browse/HCATALOG-499
> Project: HCatalog
> Issue Type: Bug
> Affects Versions: 0.4.1
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Fix For: 0.5, 0.4.1
>
> Attachments: HCATALOG-499.patch
>
>
> There is change in the semantics of
> JobContext::JobContext(Configuration, JobID). While in .20, the Config was
> cloned, in .23 the Config is adopted (if it's a JobConf). That combined with
> the way mapred Task.java handles output committers that do not extend
> FileOutputCommitter has broken storing different partitions to the same table
> with multiple store statements in pig.
--
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
