[SPARK-43838][SQL][FOLLOWUP] Replace HashSet
with HashMap
to improve performance of DeduplicateRelations
#48392
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.
What changes were proposed in this pull request?
This PR replaces
HashSet
that is currently used with aHashMap
to improveDeduplicateRelations
performance.Additionally, this PR reverts #48053 as that change is no longer needed
Why are the changes needed?
Current implementation doesn't utilize
HashSet
properly, but instead performs multiple linear searches on the set creating a O(n^2) complexityDoes this PR introduce any user-facing change?
How was this patch tested?
Existing tests
Was this patch authored or co-authored using generative AI tooling?