[ https://issues.apache.org/jira/browse/AVRO-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johannes Schulte updated AVRO-1239: ----------------------------------- Status: Patch Available (was: Open) keep > AvroMultipleOutput ignores schemas > ---------------------------------- > > Key: AVRO-1239 > URL: https://issues.apache.org/jira/browse/AVRO-1239 > Project: Avro > Issue Type: Bug > Components: java > Affects Versions: 1.7.3 > Reporter: Johannes Schulte > Priority: Minor > Labels: avro, mapreduce > > Adding namedOutputs with AvroMultipleOutputs.addNamedOutput just adds them to > a static map which is of course not available on the cluster during reduce > execution. > The unit tests pass though since the Instance of AvroMultipleOutputs is the > same in the Reducer as in the Job's main class, so the added schemas there > are present. > Fix would be to add the namedOutput schemas to the job configuration so they > can be parsed in the reducers. Example patch for the new mapreduce api is > attached, but I suspect the problem is present in the mapred api also. What > is the general approach for this? Fix both? > Cheers, > Johannes -- 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