feat(csharp/src/Drivers/Databricks): Added connection params of rateLimitRetry and rateLimitRetryTimeout #3612
+189
−40
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.
Summary
Adds support for separate retry configuration for HTTP 429 (Too Many Requests) responses, allowing independent control of rate limit retry behavior from other retryable errors (408, 502, 503, 504).
Changes Made
adbc.databricks.rate_limit_retry(boolean, default: true): Controls whether to retry HTTP 429 (TooManyRequests) responses. Can be disabled independently from other retry typesExample:
"adbc.databricks.rate_limit_retry": "false"adbc.databricks.rate_limit_retry_timeout(integer, default: 120 seconds): Maximum total time in seconds to retry HTTP 429 responses before failing. Set to 0 to retry indefinitelySeparate from the
TemporarilyUnavailableRetryTimeout(900 seconds for 408/502/503/504)Example:
"adbc.databricks.rate_limit_retry_timeout": "60"