On Thu, May 9, 2019 at 4:44 PM Wes McKinney wrote:
> hi Ravi,
>
> It's hard to say anything without looking at some code. Are you
> working on a pull request? This seems like potentially useful
> functionality to have in the project.
>
We are currently developing on an internal netflix fork so I'
Weihua Jiang created ARROW-5300:
---
Summary: 0.13 FAILED to build with option
-DARROW_NO_DEFAULT_MEMORY_POOL
Key: ARROW-5300
URL: https://issues.apache.org/jira/browse/ARROW-5300
Project: Apache Arrow
Benjamin Kietzman created ARROW-5299:
Summary: [C++] ListArray comparison is incorrect
Key: ARROW-5299
URL: https://issues.apache.org/jira/browse/ARROW-5299
Project: Apache Arrow
Issue Ty
Op do 9 mei 2019 om 21:38 schreef Uwe L. Korn :
> +1 to the idea of adding a protocol to let other objects define their way
> to Arrow structures. For pandas.Series I would expect that they return an
> Arrow Column.
>
> For the Arrow->pandas conversion I have a bit mixed feelings. In the
> normal
My initial idea was to not let this protocol pass metadata around (which
indeed is not possible for arrays).
Currently, metadata are only saved at the level of a Table when converting
from a pandas DataFrame (in Table.from_pandas()). That could continue to be
the case, where Table.from_pandas both
