-
Notifications
You must be signed in to change notification settings - Fork 4k
GH-49081: [C++][Parquet] Correct variant's extension name #49082
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
base: main
Are you sure you want to change the base?
Conversation
|
|
| explicit VariantExtensionType(const std::shared_ptr<::arrow::DataType>& storage_type); | ||
|
|
||
| std::string extension_name() const override { return "parquet.variant"; } | ||
| std::string extension_name() const override { return "arrow.parquet.variant"; } |
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.
This change looks good.
Do you think it is worth adding a kVariantExtensionName in this file and move this file to cpp/src/arrow/extension/parquet_variant.h?
WDYT? @pitrou
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.
JsonExtensionType also uses hardcoded extension name. If we want to define string literals, I suggest to move other's extension types' names into a same file.
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.
Do we need to move variant_internal.h to cpp/src/arrow/extension/ like other extension types?
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.
Yes, that's exactly what I proposed above.
Rationale for this change
Correct variant extension according to arrow's specification.
What changes are included in this PR?
Modified variant's hardcoded extension name.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.