[
https://issues.apache.org/jira/browse/AVRO-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750022#action_12750022
]
Doug Cutting commented on AVRO-91:
----------------------------------
> One drawback of having {read,write}{Record,Union}{Start,End} methods is that
> all clients that use decoder/encoder
> will have to generate these calls. This could be cumbersome for the clients
> and/or have performance impact.
There are not many clients. Mostly it's just generic, since specific inherits
from that, no? So this is only a problem if we expect applications to code
directly to the Encoder/Decoder API. The Java parser was implemented with that
in mind, so that folks could, e.g., write data in a streaming manner, without
ever building objects. Do we expect folks to do this much in Python?
As for performance, I would not expect two no-op method calls per record and
union would impact things much.
> add json codec in python
> ------------------------
>
> Key: AVRO-91
> URL: https://issues.apache.org/jira/browse/AVRO-91
> Project: Avro
> Issue Type: New Feature
> Components: python
> Reporter: Doug Cutting
> Assignee: Ravi Gummadi
>
> Now that AVRO-50 is complete, it would be good to have a Json encoder and
> decoders in Python.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
