Cleans up some of the redundant code in proxy/internal RAPIDS Shuffle Managers [databricks] #6030
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: Alessandro Bellina abellina@nvidia.com
Closes #3624.
I am looking to cleanup some of the proxy/base/internal classes in RapidsShuffleManager as per the issue @gerashegalov raised a while back. As it is now, each shim has 3 things:
ProxyRapidsShuffleInternalManager
)ProxyRapidsShuffleInternalManagerBase
)RapidsShuffleInternalManagerBase
)And essentially the
RapidsShuffleManager
(aka the proxy) loads the internal manager later in time. We have different versions of this so we get one specific to each shim, for binary compatibility reasons.This change mainly moves
getReader
back to theRapidsShuffleInternalManagerBase
so we can remove some redundant code (this path was the same everywhere I saw). It also renamesVisibleShuffleManager
toRapidsShuffleManagerLike
, but this is not something I feel too strongly about. @gerashegalov could you take a look to see if you have other recommendations that can be done here?There's more that can be done, for example
ShuffleManager
is consistent for all the spark versions we support (well not sure about the vendor specific ones as much), so we could in theory have a singleRapidsShuffleManager
that really just subclasses fromProxyRapidsShuffleInternalManagerBase
directly and also implementsShuffleManager
... but that seems like a bigger change.