-
Notifications
You must be signed in to change notification settings - Fork 431
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
GH-465: Clarify backward-compatibility rules on LIST type #466
base: master
Are you sure you want to change the base?
Conversation
abc3d1d
to
d9579bc
Compare
BTW, can you also point out the Java code in this pr? |
Other LGTM but I think it worths issue a disscussion... |
4551c79
to
f200d34
Compare
I have sent a discussion thread to the dev ML. It would be good if you can take a look. Thanks! @emkornfield @pitrou @gszadovszky @rdblue @etseidl @clairemcginty |
f200d34
to
fc8aca3
Compare
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.
Seems like a nice clarification to me. One little (ignorable) nit.
I'm also wondering if we should add an example above for the non-LIST annotated repeating fields, or should that be a new PR?
repeated type is the element type and elements are required. | ||
element type and elements are required. In this case, the element type is | ||
a Struct type with multiple fields. | ||
3. If the repeated field is a group (without annotation) with one `required` or |
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.
3. If the repeated field is a group (without annotation) with one `required` or | |
3. If the repeated field is a group (without `LIST` annotation) with one `required` or |
Not sure if this should be made explicit.
repeated type is the element type and elements are required. | ||
element type and elements are required. In this case, the element type is | ||
a Struct type with multiple fields. | ||
3. If the repeated field is a group (without annotation) with one `required` or |
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 might leave the entire block as it was previously and clarify that:
- Without annotatation the type is a single struct/tuple with the element in it.
- With a logical type annotation (I think only LIST and MAP apply here).
I also think we need to update the documentation above:
The outer-most level must be a group annotated with `LIST` that contains a
single field named `list`. The repetition of this level must be either
`optional` or `required` and determines whether the list is nullable.
To point to the fact that for backwards compatibility it can also be repeated.
Rationale for this change
The C++ reader of parquet-cpp is having a hard time to read Parquet file written by parquet-java with
parquet.avro.write-old-list-structure=true
and schema below:See apache/arrow#43994 and apache/arrow#43995
What changes are included in this PR?
Clarify the rules and add an example.
Do these changes have PoC implementations?
Not required
Closes #465