[ARROW-412] [Format] Handling of buffer padding in the IPC metadata

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Component/s: Format
• Labels: pull-request-available
• Assignee: Wes McKinney
• Reporter: Wes McKinney
• Created: 08/Dec/16 22:05
• Updated: 06/Oct/19 21:44
• Resolved: 06/Oct/19 21:44

Description

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)

Issue Links

• links to: GitHub Pull Request #4370