[
https://issues.apache.org/jira/browse/ARROW-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928404#comment-15928404
]
Julien Le Dem commented on ARROW-638:
-------------------------------------
I see several possibilities:
- first class complex types: but we have to curate types so that we don't
create too many of them.
- have two float columns: but I guess we want the two values next to each other
- have one float column where odd and even indices are the components of the
complex value: which I guess would be the same binary representation as an
array of numpy.complex values
- embed floats in a fixed_width_byte_array: we lose meaning in the metadata
but also allows a zero copy import of a numpy array.
- define a generic row/struct/compound type which is a fixed width
representation of several values: Basically the same binary representation as
the previous one but associating metadata to it.
> [Format] Add metadata for single and double precision complex numbers
> ---------------------------------------------------------------------
>
> Key: ARROW-638
> URL: https://issues.apache.org/jira/browse/ARROW-638
> Project: Apache Arrow
> Issue Type: New Feature
> Components: Format
> Reporter: Wes McKinney
>
> Numerical computing libraries like NumPy and TensorFlow feature complex64 and
> complex128 numbers
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
