Commit 8f6c6d6
[SPARK-52923][CORE] Allow ShuffleManager to control push merge during shuffle registration
### What changes were proposed in this pull request?
This PR moves the `shuffleManager.registerShuffle()` call to occur after the initialization of `_shuffleMergeAllowed` in `ShuffleDependency`.
### Why are the changes needed?
While `spark.shuffle.push.enabled` provides global control over push-based shuffle, there are scenarios requiring more granular control:
- Mass spark application migration scenarios where different jobs may need different shuffle strategies
- Remote shuffle manager(e.g. celeborn/uniffle) need shuffle-level fallback capabilities to push-based shuffle
- Dynamic decision making based on shuffle characteristics during shuffle registration
### Does this PR introduce _any_ user-facing change?
No, this is an internal refactoring that maintains backward compatibility. The default behavior remains unchanged.
### How was this patch tested?
- Existing unit tests continue to pass
- The change only affects the order of initialization, not the logic
### Was this patch authored or co-authored using generative AI tooling?
No
Closes #51629 from gaoyajun02/SPARK-52923.
Authored-by: gaoyajun02 <gaoyajun02@meituan.com>
Signed-off-by: Mridul Muralidharan <mridul<at>gmail.com>1 parent 23d9253 commit 8f6c6d6
1 file changed
+3
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
127 | 127 | | |
128 | 128 | | |
129 | 129 | | |
130 | | - | |
131 | | - | |
132 | | - | |
133 | 130 | | |
134 | 131 | | |
135 | 132 | | |
136 | 133 | | |
137 | 134 | | |
138 | 135 | | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
139 | 139 | | |
140 | 140 | | |
141 | 141 | | |
| |||
0 commit comments