[
https://issues.apache.org/jira/browse/HADOOP-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788813#action_12788813
]
Doug Cutting commented on HADOOP-6323:
--------------------------------------
> AvroSpecificSerialization calls t.getSchema() on the instance
SpecificData.get().getSchema(Class) will get the schema from a class.
One question is whether, with Avro, we want to make the setting of metadata for
a job (either the class name or a schema) required or optional. With Writable,
it has always been required, no? You need to set the job's input and output
classes. We never just guess based on the first object read or written, I
think. So, we could do that differently for Avro, instead dynamically
determining the schema or class name if it's not declared, but do we need to?
> Serialization should provide comparators
> ----------------------------------------
>
> Key: HADOOP-6323
> URL: https://issues.apache.org/jira/browse/HADOOP-6323
> Project: Hadoop Common
> Issue Type: New Feature
> Components: io
> Reporter: Doug Cutting
> Assignee: Aaron Kimball
> Attachments: HADOOP-6323.2.patch, HADOOP-6323.3.patch,
> HADOOP-6323.4.patch, HADOOP-6323.5.patch, HADOOP-6323.6.patch,
> HADOOP-6323.patch
>
>
> The Serialization interface should permit one to create raw comparators.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
