[ 
https://issues.apache.org/jira/browse/MAPREDUCE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799288#action_12799288
 ] 

Doug Cutting commented on MAPREDUCE-815:
----------------------------------------

Aaron, this sounds good.  A few questions:
 - If, in the InputFormat we populated the key rather than the value, then one 
would not even need to specify InverseMapper: by default, MapReduce would 
simply partition and sort Avro data.  Making values optional in both input and 
output seems more consistent, but does break compatibility with 
TextInputFormat.  Thoughts?
 - In the OutputFormat, should we check if values are non-null or just drop 
them?  Just dropping them may cause some confusion, but is probably useful in 
many cases, so I guess we err towards utility?

> Add AvroInputFormat and AvroOutputFormat so that hadoop can use Avro 
> Serialization
> ----------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-815
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-815
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>            Reporter: Ravi Gummadi
>            Assignee: Aaron Kimball
>
> MapReduce needs AvroInputFormat similar to other InputFormats like 
> TextInputFormat to be able to use avro serialization in hadoop. Similarly 
> AvroOutputFormat is needed.

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