Skip to content

Conversation

@wesm
Copy link
Member

@wesm wesm commented May 15, 2017

cc @TheNeuralBit -- the 64-byte padding in the C++ file writer was incorrect (http://arrow.apache.org/docs/ipc.html indicate padding to an 8-byte boundary), so this fixes that.

Change-Id: I5e209648c2947f44dfa12bb95ff9b855a410f43f
@wesm
Copy link
Member Author

wesm commented May 16, 2017

+1. Here is the appveyor build https://ci.appveyor.com/project/wesm/arrow/build/1.0.439

@asfgit asfgit closed this in ce0bb53 May 16, 2017
@wesm wesm deleted the ARROW-1002 branch May 16, 2017 01:40
jeffknupp pushed a commit to jeffknupp/arrow that referenced this pull request Jun 3, 2017
… format

cc @TheNeuralBit -- the 64-byte padding in the C++ file writer was incorrect (http://arrow.apache.org/docs/ipc.html indicate padding to an 8-byte boundary), so this fixes that.

Author: Wes McKinney <wes.mckinney@twosigma.com>

Closes apache#693 from wesm/ARROW-1002 and squashes the following commits:

35c023f [Wes McKinney] Fix C++ inconsistency with padding at start of IPC file format
pribor pushed a commit to GlobalWebIndex/arrow that referenced this pull request Oct 24, 2025
…malVector and Decimal256Vector (apache#693)

## What's Changed

This PR proposes to use the "from" `ValueVector`'s field while
transferring `DecimalVector` and `Decimal256Vector` to preserve
nullability information. This is to have similar behavior with all the
other primitive value vectors. Note that the `FieldType` of the value
vector has nullability information.

Closes apache#692 .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant