mcp: make the query tool's cluster optional so null-cluster products stay readable (DEX-71) - #38023
Draft
bobbyiliev wants to merge 1 commit into
Draft
mcp: make the query tool's cluster optional so null-cluster products stay readable (DEX-71)#38023bobbyiliev wants to merge 1 commit into
bobbyiliev wants to merge 1 commit into
Conversation
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
1 participant
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.
Discovery nulls a data product's cluster when the role lacks USAGE on its index cluster, but the
querytool required a cluster and the agent surface offers no way to discover one, so such a product was unreadable wheneverread_data_productis disabled. Omittingclusternow reads on the session's default cluster, matching whatread_data_productalready does; an explicitly empty cluster is still rejected.