Skip to content

GH-33830: Clarify handling of Null values in REE encoding #33831

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zeroshade merged 3 commits into from
Jan 23, 2023
Merged

GH-33830: Clarify handling of Null values in REE encoding #33831

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8531f8a
doc: fix REE parent null count field
zagto Jan 22, 2023
eae2b66
clarify null encoding
zagto Jan 22, 2023
51595aa
Update docs/source/format/Columnar.rst
zagto Jan 22, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/source/format/Columnar.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -815,6 +815,9 @@ A run must have have a length of at least 1. This means the values in the
run ends array all are positive and in strictly ascending order. A run end cannot be
null.

The REE parent has no validity bitmap, and it's null count field should always be 0.
Null values are encoded as runs with the value null.

As an example, you could have the following data: ::

type: Float32
Expand All @@ -824,7 +827,7 @@ In Run-end-encoded form, this could appear as:

::

* Length: 7, Null count: 2
* Length: 7, Null count: 0
* Child Arrays:

* run_ends (Int32):
Expand Down