Skip to content

Conversation

@msrathore-db
Copy link
Contributor

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

  • New Connection Parameters:
  1. adbc.databricks.rate_limit_retry (boolean, default: true): Controls whether to retry HTTP 429 (TooManyRequests) responses. Can be disabled independently from other retry types
    Example: "adbc.databricks.rate_limit_retry": "false"
  2. 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 indefinitely
    Separate from the TemporarilyUnavailableRetryTimeout (900 seconds for 408/502/503/504)
    Example: "adbc.databricks.rate_limit_retry_timeout": "60"

@msrathore-db msrathore-db marked this pull request as ready for review October 24, 2025 18:53
@github-actions github-actions bot added this to the ADBC Libraries 21 milestone Oct 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant