Add integration test for parquet async writer #11855
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jihoonson
force-pushed
the
async-parquet-it-test
branch
from
24a525f to
8b1ffa1
Compare
Signed-off-by: Jihoon Son <[email protected]>
jihoonson
force-pushed
the
async-parquet-it-test
branch
from
8b1ffa1 to
9f9902f
Compare
|
build |
revans2
approved these changes
Dec 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A follow-up to #11730. This PR adds an integration test for the async writer for Parquet. In addition, it fixes a bug that the
spark.rapids.sql.asyncWrite.queryOutput.enabledconfig was effective perSparkContext. It did not allow turning the async write on/off per query within the sameSparkContext. It should instead be per-query basis, so that each query can be optimized individually.