[
https://issues.apache.org/jira/browse/AVRO-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800254#action_12800254
]
Doug Cutting commented on AVRO-327:
-----------------------------------
In AVRO-315, Thiru said, "it's desirable to keep the property that the decoder
does not take more bytes off the input stream than necessary. That property
will allow the input stream not rewindable."
Are there important use cases where buffering is a problem? I can't think of
any, but if there are then we might support both: call Scott's implementation
BufferedBinaryDecoder and encourage folks to use that unless buffering is a
problem. Could that work?
> Performance improvements to BinaryDecoder.readLong()
> ----------------------------------------------------
>
> Key: AVRO-327
> URL: https://issues.apache.org/jira/browse/AVRO-327
> Project: Avro
> Issue Type: Improvement
> Components: java
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
>
> AVRO-315 proposed performance improvements to readLong(), readFloat() and
> readDouble(). readLong() did not improve performance well for all. Scott
> proposed a better method (but requires a change in semantics and API). We'll
> carry on the discussion on that proposal here. AVRO-315 will be committed
> with changes for readFloat() and readDouble().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
