Draft: support spark v2 write #5241
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Linked issue: part of #4816
Support spark datasource v2 write path, reduce write serialization overhead and accelerate the process of writing to primary key tables in Spark. Currently only added support for fixed-bucket table.
Tests
BucketFunctionTest, SparkWriteITCase
PaimonSourceWriteBenchmark:
API and Format
Documentation
Add a config
spark.sql.paimon.use-v2-writeto enable switching to v2 write, will fall back to v1 write when encountering an unsupported scenario(e.g.HASH_DYNAMICbucket mode table).Note: this is an overall draft PR, which will be split into smaller PRs for easier review.