[ https://issues.apache.org/jira/browse/ARROW-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wes McKinney resolved ARROW-6038. --------------------------------- Resolution: Fixed Fix Version/s: 0.15.0 Issue resolved by pull request 4983 [https://github.com/apache/arrow/pull/4983] > [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, 0.14.0, 0.14.1 > Reporter: Piotr Bajger > Priority: Minor > Labels: pull-request-available, windows > Fix For: 0.15.0 > > Attachments: segfault_ex.py > > Time Spent: 40m > Remaining Estimate: 0h > > When creating a Table from a 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.14.0 installed through pip > (problem also occurs with 0.13.0 from conda-forge). -- This message was sent by Atlassian JIRA (v7.6.14#76016)