Skip to content

Ensure thrift field IDs stay within range#276

Merged
vikrantpuppala merged 1 commit intodatabricks:mainfrom
vikrantpuppala:thrift-field-test
Jun 24, 2025
Merged

Ensure thrift field IDs stay within range#276
vikrantpuppala merged 1 commit intodatabricks:mainfrom
vikrantpuppala:thrift-field-test

Conversation

@vikrantpuppala
Copy link
Collaborator

Ensure thrift field IDs stay within range

Tested by changing a field ID to > allowed and it worked fine

Running tool: /Users/vikrant.puppala/.gvm/gos/go1.21/bin/go test -timeout 30s -run ^TestThriftFieldIdsAreWithinAllowedRange$ github.com/databricks/databricks-sql-go/internal/cli_service

=== RUN   TestThriftFieldIdsAreWithinAllowedRange
    /Users/vikrant.puppala/databricks-sql-go/internal/cli_service/thrift_field_id_test.go:49: Found Thrift field IDs that exceed the maximum allowed value of 3328.
        This can cause compatibility issues and conflicts with reserved ID ranges.
        Violations found:
          - Line 11794: Field 'maxBytesPerBatch' has ID 3356 (exceeds maximum of 3328) - MaxBytesPerBatch *int64

--- FAIL: TestThriftFieldIdsAreWithinAllowedRange (0.01s)
FAIL
FAIL    github.com/databricks/databricks-sql-go/internal/cli_service    0.841s

Signed-off-by: Vikrant Puppala <vikrant.puppala@databricks.com>
@vikrantpuppala vikrantpuppala merged commit 746c05d into databricks:main Jun 24, 2025
2 of 3 checks passed
@vikrantpuppala vikrantpuppala deleted the thrift-field-test branch June 24, 2025 06:06
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.

2 participants

Comments