Fix init order issue in GpuShuffleEnv when RAPIDS shuffle configured #518
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.
Signed-off-by: Jason Lowe jlowe@nvidia.com
This fixes an initialization ordering issue recently introduced in
GpuShuffleEnv
where it tries to access a SparkSession while it's being created and hasn't been advertised yet. It needs it for aRapidsConf
, and rather than finding another way to construct one from scratch, it turns out the caller already has one prepped. It's cheaper and simpler to just pass the existing conf.