[
https://issues.apache.org/jira/browse/AVRO-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729751#comment-13729751
]
Doug Cutting commented on AVRO-1353:
------------------------------------
> the DatumReader needs to use the class loader of the job configuration
SpecificData has a getClassLoader() method that's currently used for this.
Generalizing it to a base class sounds like the thing to do. So this is
another method that should migrate to the new abstract base class or to
GenericData in the meantime.
> if you're okay with the initial implementation using GenericData directly,
> I'm not going to argue with getting a feature I need sooner, but I'm also not
> excited about changing code again later to implement a new interface.
When we add the abstract base class we should replace references to GenericData
to instead be the new base class. Doing this back-compatibly may be difficult,
so this might be forced to go into Avro 1.8. If you need your feature in a
1.7.x release then it's probably best to use GenericData as the base.
> Configurable Hadoop serialization in-memory representations
> -----------------------------------------------------------
>
> Key: AVRO-1353
> URL: https://issues.apache.org/jira/browse/AVRO-1353
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.7.5
> Reporter: Marshall Bockrath-Vandegrift
> Attachments: avro-1353-2.patch, avro-1353.patch
>
>
> As discussed on the Avro Users mailing list [1], it would be useful to allow
> configuration of the DatumReader/Writer implementations used by Hadoop Avro
> serialization, especially for non-Java JVM languages.
> [1]
> http://mail-archives.apache.org/mod_mbox/avro-user/201305.mbox/%3C87ehdh14qn.fsf%40zeno.atl.damballa%3E
--
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
