[
https://issues.apache.org/jira/browse/ARROW-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Micah Kornfield updated ARROW-6594:
-----------------------------------
Description:
Avro supports some logical types that overlap with Arrow logical types
([http://avro.apache.org/docs/current/spec.html#Logical+Types)
|http://avro.apache.org/docs/current/spec.html#Logical+Types]
For the ones that overlap, we should use the appropriate Arrow Logical type
array instead of the raw values.
was:
It has been posited that the Decoder object (and on-heap work in general) is
potentially slow for decoding.
The scope of this Jira is to add a new method that instead of consuming from
Decoder, consumes directly from a ByteBuffer. In order to this we there needs
to be utility classes for zig-zag decoding (one might existing in avro) from a
ByteBuffer.
This is esentially rewriting logic in the decoder to work directly against a
bytebuffer and then measure if there is a meaningful performance impact.
> [Java] Support logical type encodings from Avro
> -----------------------------------------------
>
> Key: ARROW-6594
> URL: https://issues.apache.org/jira/browse/ARROW-6594
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Java
> Reporter: Micah Kornfield
> Priority: Major
> Labels: avro
>
> Avro supports some logical types that overlap with Arrow logical types
> ([http://avro.apache.org/docs/current/spec.html#Logical+Types)
> |http://avro.apache.org/docs/current/spec.html#Logical+Types]
>
> For the ones that overlap, we should use the appropriate Arrow Logical type
> array instead of the raw values.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
