[
https://issues.apache.org/jira/browse/AVRO-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800819#action_12800819
]
Doug Cutting commented on AVRO-327:
-----------------------------------
> This should work most of the time except when using a validating or resolving
> decoders, where the usage becomes somewhat cumbersome.
How would it be significantly more cumbersome than it is currently? Instead of
performing non-Avro IO on the InputStream that you passed to ValidatingDecoder
or ResolvingDecoder you'd perform non-Avro IO on the BinaryDecoder that you
passed these. If an InputStream is required for the non-Avro input, then we
can provide a non-buffered InputStream that wraps a BinaryDecoder. I don't see
applications getting much more complicated by this.
> 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.
