Add Support for Asynchronous Token Refresh #465
Merged
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 introduces a new environment variable
DATABRICKS_ENABLE_EXPERIMENTAL_ASYNC_TOKEN_REFRESHto enable asynchronous token refresh in the Databricks SDK for Java. This feature improves performance by allowing token refresh operations to happen in the background, reducing latency for API calls.This change activates the asynchronous refresh capability that was previously added in #455. When enabled, stale tokens will trigger a background refresh while expired tokens will still block until a new token is fetched.
How to Enable Async Token Refresh
Set the environment variable:
export DATABRICKS_ENABLE_EXPERIMENTAL_ASYNC_TOKEN_REFRESH=trueThis setting will be automatically picked up by the SDK and applied to all token refresh operations.
How is this tested?
Manual verification that existing unit tests and integration tests pass with both async refresh disabled and enabled.