Skip to content

acceptance: sort get-index schema_json in vector search schema_normalization test #5631

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
janniklasrose merged 1 commit into from
Jun 17, 2026
+4 −3
Merged

acceptance: sort get-index schema_json in vector search schema_normalization test #5631

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions acceptance/bundle/resources/vector_search_indexes/schema_normalization/script
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,11 @@ trap cleanup EXIT

trace $CLI bundle deploy

# The backend (and the test server) rewrite the schema on create, so
# get-index returns Spark type names and sorted keys, not the config literal.
# The backend (and the test server) rewrite the schema on create, so get-index
# returns Spark type names, not the config literal. The backend does not
# guarantee column order, so sort keys to keep this comparison stable.
index_name="main.default.vs_index_${UNIQUE_NAME}"
trace $CLI vector-search-indexes get-index "${index_name}" | jq -r '.direct_access_index_spec.schema_json'
trace $CLI vector-search-indexes get-index "${index_name}" | jq -rcS '.direct_access_index_spec.schema_json | fromjson'

# Re-plan must be a no-op: remote changes to schema_json are ignored
# (ignore_remote_changes), so the immutable spec does not plan a recreate.
Expand Down
Loading