[
https://issues.apache.org/jira/browse/AVRO-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985210#action_12985210
]
Scott Carey commented on AVRO-726:
----------------------------------
Hi Xiaolu,
These features sound very interesting and useful. I would love to see a patch
and figure out how to incorporate similar features. Even if we go in a
slightly different direction, I think all your needs are things I would like to
address:
1/2) reduce cost of autoboxing and memory footprint of objects.
3) Solutions for mapping inheritance to avro.
4) Callbacks -- I would need to see what you did here and some example use
cases -- are these for users or the internal framework?
5) Generating code that instantiates objects with the builder pattern and
avoids publicly exposed variables has been discussed many times here, I
definitely want to have that built-in to Avro.
> Make GenericDatumReader/GenericDatumWriter data member protected so that it
> can be used by the derived classes
> --------------------------------------------------------------------------------------------------------------
>
> Key: AVRO-726
> URL: https://issues.apache.org/jira/browse/AVRO-726
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.5.0
> Reporter: Xiaolu Ye
> Fix For: 1.5.0
>
>
> Currently, GenericDatumReader/GenericDatumWriter data members are private. Is
> it possible to make them protected so that we could extend those classes and
> create our own special DatumReader/Writer? The reason we want to do that is
> because we've created our own base SpecificRecordEx that implements
> SpecificRecord and added put/get for primitive types. We now want to extend
> the GenericDatumReader/GenericDatumWriter to use those primitive put/get
> functions to reduce box/unbox for better performance.
> Thanks,
> Xiaolu
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
