Repository navigation
perf: skip gzip for SEA responses by default - #1723
Merged
rahuls-db merged 1 commit intoOct 6, 2026
Merged
Conversation
Signed-off-by: Rahul Singhal <rahul.singhal@databricks.com>
rahuls-db
marked this pull request as ready for review
October 6, 2026 18:07
vuanhphung
approved these changes
Oct 6, 2026
rahuls-db
deleted the
rahul-singhal_data/rahul-singhal/sea-disable-response-gzip
branch
October 6, 2026 20:30
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
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.
Description
Disables HTTP response compression by default for SQL Execution API requests by sending
Accept-Encoding: identity. SEA inline results are already LZ4-compressed Arrow encoded in JSON, so the additional gzip layer adds server and client work.The behavior is scoped to the SEA API client; OAuth, Thrift, CloudFetch, telemetry, and other HTTP traffic are unchanged. Bandwidth-constrained clients can restore the prior behavior with
EnableSeaResponseCompression=1.Testing
mvn -pl jdbc-core test -Dtest=DatabricksConnectionContextTest,DatabricksSdkClientUserAgentTest— 164 passed, 0 failed.jdbc-coresuite was attempted, but the pre-existingDatabricksArrowPatchTest.testConcurrentExecutionstress test did not complete after several minutes and was stopped; no failures occurred before that test.Telemetry Errors
DatabricksDriverErrorCodewhere appropriate, and any new code is uniquely numbered and tested.Additional Notes to the Reviewer
This mirrors adbc-drivers/databricks#678 for the JDBC driver independent SEA implementation.