Skip to content

fix: retry Thrift requests on the same statuses and network errors as the kernel - #605

Open
vuanhphung wants to merge 15 commits into
mainfrom
fix/thrift-retry-open-session-and-rejected-execute
Open

vuanhphung wants to merge 15 commits into
mainfrom
fix/thrift-retry-open-session-and-rejected-execute

Conversation

@vuanhphung

@vuanhphung vuanhphung commented Nov 13, 2026 •

Copy link
Copy Markdown
Collaborator

Problem

On the Thrift backend a single transient HTTP error fails the connection or the statement, while the kernel (SEA) backend retries it: OpenSession is never retried, ExecuteStatement fails on a 429 or a 503 with Retry-After (the server didn't run it), 408 isn't retried, and Retry-After's value has no effect. More generally, Thrift and the kernel retry different sets of statuses and network errors.

Found by the cross-driver specs ERRORRECOV-001, 007–012 and SESSION-013: live runs on main through the test proxy show 1 Thrift attempt in every case, while the SEA leg (and the C#, Go and Python Thrift drivers) retry and pass.

Change

Which requests are retried now matches the kernel per request class (src/client/retry.rs RetryStrategy, plus its CloudFetch chunk retry), except for the differences listed at the end, in one shared classification in HttpRetryPolicy.ts (isRetryableStatus, isConnectError, PERMANENT_NETWORK_ERROR_CODES). Node's own backoff, jitter and budget stay. Rule, per the user: add the retries Node is missing, undo the differences this PR introduced, and keep pre-existing Node retries the kernel doesn't do, except certificate failures and ENOTFOUND, which the user chose to stop.

request class kernel Node
idempotent RPCs CreateSession, CloseSession, GetStatementStatus, CancelStatement, CloseStatement, ExecuteMetadataQuery (retry.rs:93-98) OpenSession (added) and the other retryableThriftMethods (ThriftHttpConnection.ts:79)
non-idempotent ExecuteStatement ExecuteStatement (NonIdempotentRequestRetryPolicy, renamed from #598's UnsentRequestRetryPolicy, which isn't exported or released)
CloudFetch download CloudFetchDownload + chunk retry (streaming_provider.rs:1116-1176) CloudFetchResultHandler (getRetryPolicy('cloudFetch'))
feature flags single attempt (feature_flags/mod.rs:330-366) retried with the RPC classification (pre-existing, kept, total-time capped; FeatureFlagCache.fetchWithRetry)
no 1:1 GetResultChunks (by chunk index) FetchResults advances the cursor, so it stays unretried; delegation-token RPCs unretried

Retried? (main → this PR; ✓ = same as the kernel)

condition kernel idempotent kernel ExecuteStatement Node RPC Node ExecuteStatement Node CloudFetch
2xx / 3xx no no no ✓ no ✓ no ✓
400, 401, 403–405, 409–416 no (CloudFetch chunk loop: yes) no no ✓ no ✓ no (chunk-loop 4xx with link refresh: #610)
408 yes no no → yes ✓ no ✓ no → yes ✓
429 yes yes yes ✓ (OpenSession: no → yes) no → yes ✓ yes ✓
other 4xx (402, 406, 407, 417, 418, 421–426, 428, 431, 451, …) yes no no → yes ✓ no ✓ no → yes ✓
501 yes no no → yes ✓ no ✓ no → yes ✓
500, 502, 504, other 5xx yes no yes ✓ no ✓ yes ✓
503 with / without Retry-After yes / yes yes / no yes / yes ✓ no → yes / no ✓ yes / yes ✓
refused, EAI_AGAIN yes yes yes ✓ yes ✓ yes ✓
connect timeout, EHOSTUNREACH, ENETUNREACH (one address, or every address of a host with several), socket closed during the TLS handshake yes yes yes ✓ no → yes ✓ yes ✓
non-certificate TLS protocol/alert error during the handshake yes yes yes ✓ no (missing: not detected; accepted gap, follow-up) yes ✓
reset, EPIPE, socket hang up after sending yes no yes ✓ no ✓ yes ✓
no response within the timeout yes no no → yes ✓ (if retriesTimeout leaves time, so not with the defaults; the error stays Request timed out) no ✓ n/a (no per-attempt timeout; stalls: #610)
body-phase error (premature close, body timeout) no for RPCs (body read after the loop, http.rs:943-952); yes for CloudFetch no yes (pre-existing #424, kept; now also on OpenSession, which main didn't retry at all) no ✓ yes ✓
certificate verification failure (named codes, and UNSPECIFIED, Node's code for every X509 error it doesn't name) no no yes → no ✓ no ✓ yes → no ✓
ENOTFOUND no; CloudFetch chunk loop: yes no yes → no ✓ yes → no ✓ yes ✓
feature-flag fetch single attempt as Node RPC (pre-existing, kept), within one 10 s deadline for all attempts, waits and the body, so connect() isn't stretched
CloudFetch Arrow decode error CloudFetch chunk loop: yes no (follow-up: not a transport error, so out of scope here and in #610)

Retry-After changes whether a retry happens only for a 503 on ExecuteStatement, on both sides. When present, the wait is the header's value in seconds, clamped to [retryDelayMin, retryDelayMax], and a wait that would end after retriesTimeout isn't started, as the kernel does.

Once the retries this PR adds run out, a Thrift call fails with the error main gave it: THTTPException (statusCode, response and the #467 server detail), or the network error for OpenSession, as #598 already does for ExecuteStatement connect failures. Idempotent RPCs keep main's HiveDriverError on the statuses below 100, 429, 5xx-except-501 and network errors they already retried (getRetryExhaustedError in ThriftHttpConnection.ts); a CloudFetch download that runs out of retries fails with RetryError. A CloudFetch error thrown without retrying is described by its code, so its message doesn't carry the presigned URL.

Size: 235 changed non-test lines in lib/ (174 added, 61 removed); 23 of them are the list of certificate error codes.

Verification

  • npm test (1840 passing), npm run lint, npm run type-check, prettier. Through ThriftHttpConnection against a local server, the errors once retries run out (OpenSession 503/429/501 and a refused or reset connection, GetOperationStatus 408/501, ExecuteStatement 429 and 503 with Retry-After: 9 tests fail on 26abeb4) and the guards that GetOperationStatus on a 503, a status below 100 (raw HTTP/1.1 099 status line) or a refused connection keeps the RetryError. An OpenSession over TLS with a cert that Node rejects as UNSPECIFIED (generated per run with openssl, like HttpConnection.test.ts, so no key is committed) fails at once with that error, and the rpc and CloudFetch policies don't retry it (4 tests fail on 26abeb4). Every row that changed has a unit test that fails on c6b3606 (before the parity change), including the status table, ExecuteStatement 429 and connect failures (also a real multi-address connect failure through ThriftHttpConnection), the RPC request timeout end to end through ThriftHttpConnection (and Request timed out when the timeouts use up the attempts or retriesTimeout, which the e2e Timeouts tests pin), and CloudFetch ENOTFOUND. With the default retry settings, a flags endpoint that keeps failing (503 with Retry-After: 60) or never responds falls back to defaults at the deadline; both tests hang without it.
  • With the real Thrift client and commands against a local server (retryMaxAttempts: 3), on main → this head: OpenSession 503/429/502/408/501, GetOperationStatus 408/501/402, ExecuteStatement 429 and 503 with Retry-After fail with the same THTTPException (status and server detail; 1 → 3 requests), OpenSession refused with the same FetchError ECONNREFUSED, GetOperationStatus 503 and refused with the same HiveDriverError. With the default retry settings, an OpenSession whose cert fails as UNSPECIFIED (a CA without keyCertSign, an unhandled critical extension, a SHA-1 signature) fails at once with the reason, as on main; 26abeb4 took 5 connections and 30 s and hid it behind a HiveDriverError.
  • driver-test Node.js Integration Tests (replay, thrift and sea) on dd04e5f: run 44020351876 passed. Since then lib/ changed only by the status-below-100 clause, which no recording can reach. The e2e jobs on Node 22, 24 and 26 passed too.
  • Live through the driver-test proxy on the pecotesting warehouse, Thrift (kernel 0b5d0ed), on 26abeb4 (the commits after it change only the error once retries run out and UNSPECIFIED, not the attempts below):
spec main this PR
ERRORRECOV-001 (503 + Retry-After 2 s, then 4 s, on ExecuteStatement) 1 attempt, THTTPException 503 3 attempts, 6.2 s, row returned
ERRORRECOV-007 (one 503 + Retry-After on SELECT, INSERT, UPDATE, DELETE) 1 attempt 2 attempts each
ERRORRECOV-008/009/011 (503, 429, 502, 504, 408 on OpenSession) 1 attempt 2 attempts, ~2.1 s, session usable
ERRORRECOV-010/012 (persistent 429/503/502/504, retriesTimeout 1 s vs 5 s) 1 vs 1 attempt 2 vs 3 attempts
SESSION-013 (503, 408, 429, 502, 504 on OpenSession) 1 attempt 2 attempts, ~2.1 s
AUTH-017/018 (untrusted cert, hostname mismatch), invalid host pass pass

Earlier heads of this PR ran the same rows 3 times each with the same results.

Driver-test follow-ups after merge

  • RetryStatusCodesTests Thrift "503 on ExecuteStatement — driver does NOT retry": its scenario's 503 carries Retry-After, so it now sees 5 attempts instead of 1. Its Thrift 429/503-with-Retry-After cases (skipped as PECO-3071) can be enabled.
  • SESSION-011 Thrift (databricks/databricks-driver-test#2075): a request timeout on OpenSession is now retried, as the kernel does, and the delay scenario disables itself after one trigger, so the retry succeeds (live: 22.2 s, no error).
  • The xfail tripwires in databricks/databricks-driver-test#2074 and #2075 throw XPASS. #2074's ERRORRECOV-001 note that Retry-After is ignored, and the ERRORRECOV-004 Node skip reason (a dropped OpenSession isn't retried), are now stale.

Still different from the kernel

  • A non-certificate TLS protocol/alert error during the handshake (for example EPROTO wrong version number) isn't retried on ExecuteStatement: missing, not detected (accepted gap, see follow-ups). node-fetch keeps only the code and message, and the same codes can come after the request is sent. These are mostly configuration errors (wrong port or TLS version) that a retry can't fix. A socket closed during the handshake is retried.
  • Body-phase retries on RPCs (pre-existing, kept), which through OpenSession joining the idempotent RPCs now also apply to it.
  • FetchResults (no 1:1 equivalent).
  • The CloudFetch chunk loop's retries of 400–416 and stalls, with link refresh (fix: retry one-shot Thrift CloudFetch 401/403/404 downloads and time out stalled attempts #610).
  • The feature-flag fetch retries (pre-existing, kept, total-time capped at 10 s); the kernel makes one attempt.
  • Backoff, not classification: Retry-After as an HTTP date; the kernel's retriesTimeout guard also covers exponential waits.

Follow-ups

  • Retry a TLS handshake protocol error on ExecuteStatement, which needs tracking each socket's connect phase.
  • Retry CloudFetch Arrow decode errors, as the kernel's chunk loop does. It isn't a transport error, so it's out of scope here and in fix: retry one-shot Thrift CloudFetch 401/403/404 downloads and time out stalled attempts #610.
  • Drain the body of a non-200 response before retrying, so the keep-alive socket is freed sooner. This predates the PR, but more statuses are retried now.

This pull request and its description were written by Isaac.

@peco-review-bot peco-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: 1 Low

Looks good: one low concern about changelog wording. The retry classification is right: 429 and 503+Retry-After retry on ExecuteStatement, the ambiguous statuses don't, and OpenSession now uses the idempotent policy. Tests cover each case at the policy level and in the end-to-end connection tests. Follow-up work outside this PR: the existing Retry-After seconds-vs-milliseconds mismatch in getRetryAfterHeader, which the description already mentions.

Comment thread CHANGELOG.md Resolved

@peco-review-bot peco-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No issues identified by the review bot.

@vuanhphung
vuanhphung force-pushed the fix/thrift-retry-open-session-and-rejected-execute branch from 2cbb8c0 to 79ae23e Compare November 15, 2026 07:22

@peco-review-bot peco-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No issues identified by the review bot.

@peco-review-bot peco-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No issues identified by the review bot.

@peco-review-bot peco-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: 1 Nit

Looks good, nothing above nit. I traced the routing in ThriftHttpConnection.getRetryPolicy, the shared planRetry budget and how BaseCommand turns RetryError into HiveDriverError. They match the PR description and the changelog's note on the behavior change, and the unit and connection-level tests cover the new status and Retry-After paths.

Other findings

  • ⚪ Nit — NonIdempotentRetryPolicy.isRetryable decides on response.headers.has('Retry-After'), so a 503 with an empty or unparsable Retry-After still counts as "not run" and is retried with exponential backoff. That is probably what you want (the header being present is what signals intent), but a test case pinning it down would document the choice.

@vuanhphung

Copy link
Copy Markdown
Collaborator Author

Re the nit on NonIdempotentRetryPolicy.isRetryable (979bb18): keying on the header's presence is deliberate and matches the kernel, which sets has_retry_after = retry_after.is_some() from the raw header before parsing it (src/client/http.rs:958-962) and passes that to is_retryable_status (retry.rs:244). An empty or unparsable value then backs off exponentially on both backends. I'll add a test that pins it with the next change to this branch rather than push again for a test-only nit.

…ment

Thrift OpenSession was never retried, so a single 503, 429, 502, 504 or
408 failed the connection, and ExecuteStatement failed on a 503 with
Retry-After, which the server returns without running the statement.
The kernel backend retries both.

OpenSession joins the idempotent methods, HttpRetryPolicy retries 408,
and ExecuteStatement is also retried on a 503 with Retry-After. So that
a wrong host or an untrusted certificate on OpenSession isn't retried
for the whole budget and doesn't lose its cause, the shared classifier
no longer retries certificate verification failures or ENOTFOUND, as in
the kernel. After other network errors the retry-exhaustion message
names the error code, and a CloudFetch error thrown without retrying no
longer carries the presigned URL.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
@vuanhphung
vuanhphung force-pushed the fix/thrift-retry-open-session-and-rejected-execute branch from 979bb18 to a9a6052 Compare November 16, 2026 02:07

@peco-review-bot peco-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: 2 Medium · 1 Low · 1 Nit

Needs changes. The diff and the PR description disagree: there is no OpenSessionRetryPolicy, no 429 retry on ExecuteStatement, no rename and no Retry-After unit fix. OpenSession retries network errors, which the description says it must not do. The description, CHANGELOG and code should be brought into line before merge.

Other findings

  • ⚪ Nit — The PR description says ExecuteStatement "also retries 429 and 503 with Retry-After, the kernel's non-idempotent status rule" and that UnsentRequestRetryPolicy is renamed NonIdempotentRetryPolicy. Here isRetryable accepts only 503 + Retry-After, the class keeps its old name, and the new ThriftHttpConnectionRetry and UnsentRequestRetryPolicy tests assert that 429 is not retried. The CHANGELOG entry also leaves out 429. Decide which behavior is intended and align the code, tests, CHANGELOG and description. As it stands, the ERRORRECOV-009/010 (429) results in the description can't come from this diff.

@vuanhphung vuanhphung changed the title fix: retry Thrift OpenSession and server-rejected ExecuteStatement fix: retry Thrift OpenSession and a 503-with-Retry-After ExecuteStatement Nov 16, 2026

@peco-review-bot peco-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: 1 Nit

Looks good. I found no correctness issues. The shared status and connect-error rules, the Retry-After change from seconds to milliseconds (and its check against retriesTimeout), the request-timeout unwrapping, and the feature-flag deadline (AbortSignal.timeout is fine on the supported Node ≥22) all hold up when traced through invokeWithRetry, UnsentRequestRetryPolicy and describeDownloadError. One follow-up that this PR didn't introduce but now matters more since more statuses are retried: ThriftHttpConnection doesn't drain the body of a non-200 response before retrying, so keep-alive sockets can be held a little longer.

Other findings

  • ⚪ Nit — In HttpRetryPolicy.test.ts, the second loop under 'should check if HTTP transaction is safe to retry' (statuses 402, 406, …, 501) tests nothing the full 1–999 sweep above it doesn't already cover. You could drop it, or keep it as documentation and label it that way.

@vuanhphung

Copy link
Copy Markdown
Collaborator Author

On the review of 26abeb4:

  • Nit (the second status loop in HttpRetryPolicy.test.ts): it's on purpose. The 1–999 sweep checks the kernel rule, and the second loop lists the statuses whose answer changed against main (the table's "no → yes" rows), so they're named explicitly. Leaving it.
  • Not draining a non-200 body before retrying: agreed, this predates the PR (main retries 429/5xx the same way), and more retried statuses make it matter more. Noted as a follow-up rather than added here.

vuanhphung and others added 4 commits November 17, 2026 04:44
…yPolicy

The policy now retries a non-idempotent request whenever the server
didn't run it: a failure to connect, a 429, or a 503 with Retry-After.
That's more than an unsent request, so name it for the requests it
serves. It isn't exported and hasn't been released (#598), so no alias
is needed. No behavior change.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
OpenSession, ExecuteStatement on a 429 or a 503 with Retry-After, and
idempotent RPCs on statuses main didn't retry (408, 501, other 4xx)
failed with THTTPException, which carries statusCode, the response and
the server's detail, or, for OpenSession, with the network error. Once
their new retries ran out they failed with a HiveDriverError that has
none of these. Throw the last attempt's error instead, as the
ExecuteStatement connect-failure retry already does. Retries that
idempotent RPCs made before (429, 5xx except 501, network errors) keep
failing with the HiveDriverError.

BaseCommand no longer needs to name the network error code, which only
mattered for OpenSession, so it is back as on main.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
Node names 28 OpenSSL certificate verification errors and reports every
other one with the code UNSPECIFIED (ncrypto's X509Pointer::ErrorCode),
for example a CA without keyCertSign, an unhandled critical extension or
a SHA-1 signature. The certificate list missed it, so OpenSession
retried such a failure for the whole default budget (about 30 s), and
CloudFetch downloads retried it too. Treat it as a certificate failure,
which the kernel never retries either.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
…t one

Rewrite the #605 entry as short sentences on what is now retried, what
no longer is, Retry-After, the feature-flag cap and the error once
retries run out, which is now the original error for calls that weren't
retried before. Merge #458's ExecuteStatement connect-failure entry,
which #605 broadens to any failure to connect and narrows to drop
ENOTFOUND.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>

@peco-review-bot peco-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: 1 Low

Looks good, with one low concern: the CHANGELOG entry doesn't mention that a public error type changes. I traced the status and connect-error classification, the Retry-After handling and its budget check, which error is thrown once retries run out (THTTPException, RetryError or the network error), and the feature-flag fetch deadline. All match the tests and the description; AbortSignal.timeout is available on every Node version the package supports (≥22).

Comment thread CHANGELOG.md Resolved
Idempotent RPCs used to retry these and then fail with HiveDriverError;
now they fail at once with the node-fetch FetchError. Say so, and limit
the HiveDriverError sentence to the network errors still retried.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>

@peco-review-bot peco-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No issues identified by the review bot.

vuanhphung and others added 2 commits November 17, 2026 05:24
main retried a status below 100 on idempotent RPCs, as it did a 429 and
a 5xx other than 501, and ended in HiveDriverError. Include it in the
statuses whose retry exhaustion keeps the RetryError, so that row
doesn't change either.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
Six short sentences: what is now retried, ExecuteStatement, what is no
longer retried, Retry-After and the feature-flag cap, and the error once
retries run out. Drop the previously-was asides, the CloudFetch message
format (#471 documents it) and the retriesTimeout guard on Retry-After.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>

@peco-review-bot peco-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No issues identified by the review bot.

The last sentence said newly retried statuses keep their old error, which
isn't true for CloudFetch: a 501 there used to be a plain Error and now
ends as RetryError. Name CloudFetch first so the claim covers only Thrift
calls.

Co-authored-by: Isaac <no-reply@databricks.com>
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>

@peco-review-bot peco-review-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: 2 Nit

Looks good, no blocking issues; I traced the retry classification, the unwrapping of exhausted retries and the feature-flag deadline, and found only two nits. Possible follow-up: isConnectError treats any FetchError whose message ends in reason: as a failure to connect; that rests on how Node reports an AggregateError, so it's worth checking against future Node versions.

Other findings

  • ⚪ Nit — CloudFetchResultHandler.describeDownloadError now also rewrites a FetchError thrown without retrying, such as a certificate failure, to CloudFetch result download failed: network error <code>. That drops node-fetch's readable reason (e.g. unable to verify the first certificate). Dropping it keeps the presigned URL out of the message, so the trade-off is reasonable. The CHANGELOG entry still says these failures "fail at once with node-fetch's FetchError" without mentioning the new message, and a sentence there would help callers who match on the message.
  • ⚪ Nit — In FeatureFlagCache.fetchWithRetry, the 10 s FETCH_DEADLINE_MS signal now limits the whole fetch, retries included, so the per-attempt timeout: 10000 in fetchFeatureFlags can never fire first. It is redundant, and a comment or removing it would make the deadline easier to follow.

@vuanhphung

Copy link
Copy Markdown
Collaborator Author

On the review of 271d2d5 (2 nits), both left as they are:

  • CloudFetch message for a certificate failure: that message format was dropped from the entry on purpose, to keep it short as the user asked (it was in an earlier revision). The entry still says what callers can match on: the failure is the node-fetch FetchError, with its code. Only the message has the CloudFetch result download failed: network error <code> prefix, which keeps the presigned URL out of it.
  • timeout: 10000 in fetchFeatureFlags: it predates this PR and is harmless, since the 10 s deadline now bounds the whole fetch. Removing it isn't needed for this change, so I'm keeping the diff minimal.

@vuanhphung vuanhphung added the skip-coverage Skip the coverage fan-out for this PR (no tracking issue opened in databricks-driver-test) label Nov 17, 2026

This branch was successfully deployed

1 active deployment
azure-prod — 271d2d50 Deployed Nov 17, 2026 by vuanhphung via e2e-test (26.12.1, 26_12_1) #2092
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-coverage Skip the coverage fan-out for this PR (no tracking issue opened in databricks-driver-test)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant