Skip to content

Conversation

@HuaHuaY
Copy link
Contributor

@HuaHuaY HuaHuaY commented Jan 30, 2026

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.

@HuaHuaY HuaHuaY requested a review from wgtmac as a code owner January 30, 2026 10:35
@github-actions
Copy link

⚠️ GitHub issue #49081 has been automatically assigned in GitHub to PR creator.

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"; }
Copy link
Member

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

Copy link
Contributor Author

@HuaHuaY HuaHuaY Jan 31, 2026

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.

Copy link
Contributor Author

@HuaHuaY HuaHuaY Jan 31, 2026

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?

Copy link
Member

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.

@github-actions github-actions bot added awaiting committer review Awaiting committer review and removed awaiting review Awaiting review labels Jan 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

2 participants