Add a dependency on AutoValue to simplify handling of value classes. #471
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renaudhartert-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
renaudhartert-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
renaudhartert-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
renaudhartert-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
parthban-db
approved these changes
Jun 20, 2025
emmyzhou-db
approved these changes
Jun 20, 2025
Contributor
emmyzhou-db
left a comment
emmyzhou-db
left a comment
There was a problem hiding this comment.
Nice choice of class to showcase the benefits of autovalue!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 are proposed in this pull request?
This PR adds a dependency on Google's AutoValue library to simplify the development and maintenance of value classes. See Why should I use AutoValue? for more details.
The decision to use AutoValue is motivated by the fact that the Databricks SDK must support Java 8 for the foreseeable future and does not have access to new language features such as records — which would obsolete AutoValue.
NO_CHANGELOG=true
How is this tested?
Simplified one small internal class to use AutoValue and validated that the impacted unit and integration tests are fine with it.