feat: [EXPERIMENTAL] direct native shuffle execution optimization #3230
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.
Summary
This PR introduces an experimental optimization that allows the native shuffle writer to directly execute the child native plan instead of reading intermediate batches via JNI. This avoids the JNI round-trip for single-source native plans.
Current flow:
Optimized flow:
Configuration
The optimization is controlled by a new config option:
spark.comet.exec.shuffle.directNative.enabled(default:false)Scope
The optimization currently applies when:
spark.comet.shuffle.mode=native)CometNativeScanExecRangePartitioning(which requires sampling)Changes
CometShuffleDependency.scalachildNativePlanfield to pass native plan to writerCometShuffleExchangeExec.scalaCometShuffleManager.scalaCometNativeShuffleWriter.scalaCometConf.scalaCOMET_SHUFFLE_DIRECT_NATIVE_ENABLEDconfig optionCometDirectNativeShuffleSuite.scalaTest plan
CometDirectNativeShuffleSuitewith 15 tests covering:CometNativeShuffleSuitetests still pass (16/16)🤖 Generated with Claude Code