[coverage] Conformance findings: CUSTOMHDR-002
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
Research direction
Search the Go client for where Accept-Encoding or gzip transport is configured for ExecuteStatement / Statement Execution API requests (grep for Accept-Encoding, gzip, identity), and check how the HTTP client's compression settings are set up. The fix is to send identity on ExecuteStatement as the spec requires; done when TestSEARequestsDeclineResponseCompressionByDefault from the coverage PR (databricks/databricks-driver-test#1765) passes against this driver. The reference PR databricks/databricks-jdbc#1723 shows the intended behavior in another language.
Written by the indexing model from the issue text.
Description
Summary
Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-go. Each finding is committed as an expected-failure (xfail) test in the coverage PR — the test asserts the CORRECT (post-fix) behavior and stays red until THIS driver (databricks/databricks-sql-go) is fixed, then flips green as a tripwire.
Findings
- CUSTOMHDR-002 [sea]: SEA statements client sends
Accept-Encoding: gzipon ExecuteStatement instead of the explicitidentitydefault, gzipping already-compressed base64-of-LZ4-Arrow inline results (wasted CPU on both ends; the gzipped JSON envelope can be larger on the wire than the raw bytes)- failing test:
TestSEARequestsDeclineResponseCompressionByDefault(see the coverage PR diff undertests/)
- failing test:
Reproduce & Expected
CUSTOMHDR-002 — SEA (Statement Execution API) inline results are LZ4-compressed Arrow, base64-encoded and wrapped in a JSON envelope.
Reproduce:
SELECT 1 AS value
Expected (per the shared spec):
- result has exactly 1 row(s)
- col 0, row 0 == 1 (type Int32)
- full assertion contract:
result:
- row_count: 1
- column:
index: 0
row: 0
type: Int32
equals: 1
protocol:
sea:
- request_header:
operation: ExecuteStatement
name: Accept-Encoding
equals: identity
Context
- The behavior was first fixed in a DIFFERENT driver — reference PR: https://github.com/databricks/databricks-jdbc/pull/1723 — which seeded the shared language-neutral spec. This issue tracks the same conformance gap in databricks/databricks-sql-go; the reference PR is for cross-referencing the intended behavior, NOT a change to this repo.
- Coverage PR carrying the reproducing xfail test(s): https://github.com/databricks/databricks-driver-test/pull/1765
- Dominant language
- Go
- Stars
- 54
- Forks
- 71
- Avg merge
- 16h 3m
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from databricks/databricks-sql-go
-
Difficulty 4/5 3-5 days Newbie friendliness 54/100
databricks/databricks-sql-go#547 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
databricks/databricks-sql-go#546 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 1-2 days Newbie friendliness 52/100
databricks/databricks-sql-go#521 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 1-2 days Newbie friendliness 56/100
databricks/databricks-sql-go#520 ·
Maintainers usually reply within 1 day
-
engineer-bot
Difficulty 4/5 3-5 days Newbie friendliness 49/100
databricks/databricks-sql-go#517 · 3 comments ·
Maintainers usually reply within 1 day
All issues in databricks/databricks-sql-go
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
kind/features
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
TencentBlueKing/bk-nodemgr#3991 ·
Maintainers usually reply within 1 day
-
meta
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
last9/last9-mcp-server#554 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Plain-http federation signing external_url fails startup with "invalid federation request signature"Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day