[SPARK-35609][BUILD] Add style rules to prohibit to use a Guava's API which is incompatible with newer versions #32740
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 adds rules to
checkstyle.xml
andscalastyle-config.xml
to avoid introducingObjects.toStringHelper
a Guava's API which is no longer present in newer Guava.Why are the changes needed?
SPARK-30272 (#26911) replaced
Objects.toStringHelper
which is an APIs Guava 14 provides withcommons.lang3
API becauseObjects.toStringHelper
is no longer present in newer Guava.But toStringHelper was introduced into Spark again and replaced them in SPARK-35420 (#32567).
I think it's better to have a style rule to avoid such repetition.
SPARK-30272 replaced some APIs aside from
Objects.toStringHelper
butObjects.toStringHelper
seems to affect Spark for now so I add rules only for it.Does this PR introduce any user-facing change?
No.
How was this patch tested?
I confirmed that
lint-java
andlint-scala
detect the usage oftoStringHelper
and let the lint check fail.