[
https://issues.apache.org/jira/browse/AVRO-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478325#comment-13478325
]
Harsh J commented on AVRO-1179:
-------------------------------
Hi Ashish,
I think the specific error happens when you use the MO.write(KEY, VALUE,
STRING) signature, which allows MO users to generally write outputs without
defining a named output first. In this case, the STRING part is passed into the
record writer fetch call, but is ignored there.
> AvroMultipleOutputs does not seem to be generating different base output paths
> ------------------------------------------------------------------------------
>
> Key: AVRO-1179
> URL: https://issues.apache.org/jira/browse/AVRO-1179
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.7.2
> Reporter: Viji
>
> In the implementation at
> http://svn.apache.org/repos/asf/avro/trunk/lang/java/mapred/src/main/java/org/apache/avro/mapreduce/AvroMultipleOutputs.java,
> the following line in {{getRecordWriter(TaskAttemptContext taskContext,
> String baseFileName)}} has been commented out:
> {code}//FileOutputFormat.setOutputName(taskContext, baseFileName);{code}
> Hence, when we call {{mo.write(outKey, NullWritable.get(), "subdir/samp");}}
> the output still goes to the default output directory and not under the
> string path we specify.
--
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
