You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by "Piotr Bajger (JIRA)" <ji...@apache.org> on 2019/07/25 16:10:00 UTC

[jira] [Created] (ARROW-6038) [Python] pyarrow.Table.from_batches produces corrupted table if any of the batches were empty

Piotr Bajger created ARROW-6038:
-----------------------------------

             Summary: [Python] pyarrow.Table.from_batches produces corrupted table if any of the batches were empty
                 Key: ARROW-6038
                 URL: https://issues.apache.org/jira/browse/ARROW-6038
             Project: Apache Arrow
          Issue Type: Bug
    Affects Versions: 0.13.0
            Reporter: Piotr Bajger
         Attachments: segfault_ex.py

When creating a Table from an list/iterator of batches which contains an "empty" RecordBatch a Table is produced but attempts to run any pyarrow built-in functions (such as unique()) occasionally result in a Segfault.

The MWE is attached: [^segfault_ex.py]
 # The segfaults happen randomly, around 30% of the time.
 # Commenting out line 10 in the MWE results in no segfaults.
 # The segfault is triggered using the unique() function, but I doubt the behaviour is specific to that function, from what I gather the problem lies in Table creation.

I'm on Windows 10, using Python 3.6 and pyarrow 0.13.0 (py36h8c67754_1) from conda-forge.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)