You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2019/06/12 16:56:00 UTC

[jira] [Assigned] (ARROW-412) [Format] Handling of buffer padding in the IPC metadata

     [ https://issues.apache.org/jira/browse/ARROW-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wes McKinney reassigned ARROW-412:
----------------------------------

    Assignee: Wes McKinney

> [Format] Handling of buffer padding in the IPC metadata
> -------------------------------------------------------
>
>                 Key: ARROW-412
>                 URL: https://issues.apache.org/jira/browse/ARROW-412
>             Project: Apache Arrow
>          Issue Type: New Feature
>          Components: Format
>            Reporter: Wes McKinney
>            Assignee: Wes McKinney
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.14.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> See discussion in ARROW-399. Do we include padding bytes in the metadata or set the actual used bytes? In the latter case, the padding would be a part of the format (any buffers continue to be expected to be 64-byte padded, to permit AVX512 instructions)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)