Skip to content

[core] Support append read/write for MAP shared-shredding#8524

Open
lxy-9602 wants to merge 3 commits into
apache:masterfrom
lxy-9602:shredding-write-append
Open

[core] Support append read/write for MAP shared-shredding#8524
lxy-9602 wants to merge 3 commits into
apache:masterfrom
lxy-9602:shredding-write-append

Conversation

@lxy-9602

@lxy-9602 lxy-9602 commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Purpose

This is a subtask of MAP shared-shredding support.

Add append table read/write support for MAP shared-shredding.

This wires MAP shared-shredding into the append write path and ORC/Parquet read path, keeps the format layer working with physical read rows, and converts them back to logical MAP rows through the shredding read plan. It also adds end-to-end coverage for basic read/write, multiple shared-shredding MAP fields, projection, data evolution, metadata recovery, null values, overflow values, and complex value types.

This PR may look somewhat large at first glance, but more than 1600 lines are tests, and the amount of production code added is relatively limited.

Tests

  • mvn -pl paimon-common,paimon-core -am -Pfast-build -DfailIfNoTests=false -DwildcardSuites=none -Dtest=MapSharedShreddingReadPlanTest,AppendOnlyWriterTest test
  • mvn -pl paimon-core -am -Pfast-build -DfailIfNoTests=false -DwildcardSuites=none -Dtest=MapSharedShreddingTableTest test
  • mvn -pl paimon-common,paimon-core -am -DskipTests spotless:apply
  • git diff --check


private FormatWriterFactory writerFactory() {
FormatWriterFactory factory = fileFormat.createWriterFactory(writeSchema);
return ShreddingWritePlanWriterFactories.wrapMapSharedShredding(

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why wrap here? Parquet will wrap this for itsself?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MAP shared-shredding needs a MapSharedShreddingContext initialized from previous file metadata to determine the physical column count, which is difficult to handle in the format layer. That is why it is currently wrapped in AppendOnlyWriter, while Variant is wrapped inside Parquet. For consistency, would you suggest keeping this split, moving both wrappers to the writer framework, or handling both in the format layer?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I moved the wrapping into FileFormat so Variant and MAP shared-shredding share the same write path. Could you please take another look?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants