-
Notifications
You must be signed in to change notification settings - Fork 881
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.
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
Add Run End Encoding DataType #3534
Conversation
arrow-schema/src/datatype.rs
Outdated
/// | ||
/// These child arrays are prescribed the standard names of "run_ends" and "values" | ||
/// respectively. | ||
RunEndEncodedType(Box<Field>, Box<Field>), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am wondering what's the difference between using Box<Field>
vs Box<DataType>
? Dictionary
uses Box<DataType>
whereas Struct
uses Box<Field>
. I think run_ends
should just be DataType
as it's very similar to Buffer
but in child array.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Run-end encode type has child arrays with no buffers. Similar to Struct
, I treat it as two Field
s. I think it makes sense for values
to be Field
as it is possibly to be a dictionary. I remember it is necessary it to be a field for IPC serialization on dictionary. run-ends
is just primitive one, it could be just DataType
, I think.
Closing as a believe this has been superceded by #3553 |
Which issue does this PR close?
Part of #3520.
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?