[fix](split) FileSystemCacheKey are always different in overload equals #36431
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.
bp: #36432
Proposed changes
Fixed Bugs introduced from #34307
FileSystemCacheKey.equals()
compares properties by==
, resulting in creating new file system in each partitiondfsFileSystem
is not synchronized, resulting in creating more file systems than need.jobConf.iterator()
will produce more than 2000 pairs of key-value