You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Java SDK's QueryPlanRetriever.SUPPORTED_QUERY_FEATURES advertises 14 query features while the .NET SDK advertises 17. Three features are missing in Java:
Missing Feature
.NET Status
Impact
ListAndSetAggregate
✅ Sent
MAKELIST/MAKESET queries get suboptimal plans
CountIf
✅ Sent
Present in Java's QueryFeature enum but not included in the features string
Includes all of the above plus: ListAndSetAggregate, CountIf, HybridSearchSkipOrderByRewrite
Why this matters now
PR #47759 adds RNTBD header tokens (SupportedQueryFeatures 0x00FF, QueryVersion 0x0100) to transmit the feature set to the thin client proxy. The proxy uses these to determine which query plan features to include. Customers using the missing features through thin client will get degraded (less optimal) query plans.
Suggested fix
Add ListAndSetAggregate and HybridSearchSkipOrderByRewrite to QueryFeature enum (if not already present)
Add CountIf to the SUPPORTED_QUERY_FEATURES string in QueryPlanRetriever (it's already in the enum but not sent)
Add ListAndSetAggregate and HybridSearchSkipOrderByRewrite to the features string
Validate each feature against the proxy's query engine behavior
Align
SUPPORTED_QUERY_FEATURESwith .NET SDKContext
The Java SDK's
QueryPlanRetriever.SUPPORTED_QUERY_FEATURESadvertises 14 query features while the .NET SDK advertises 17. Three features are missing in Java:ListAndSetAggregateMAKELIST/MAKESETqueries get suboptimal plansCountIfQueryFeatureenum but not included in the features stringHybridSearchSkipOrderByRewriteCurrent Java feature string
.NET feature string (superset)
Includes all of the above plus:
ListAndSetAggregate,CountIf,HybridSearchSkipOrderByRewriteWhy this matters now
PR #47759 adds RNTBD header tokens (
SupportedQueryFeatures0x00FF,QueryVersion0x0100) to transmit the feature set to the thin client proxy. The proxy uses these to determine which query plan features to include. Customers using the missing features through thin client will get degraded (less optimal) query plans.Suggested fix
ListAndSetAggregateandHybridSearchSkipOrderByRewritetoQueryFeatureenum (if not already present)CountIfto theSUPPORTED_QUERY_FEATURESstring inQueryPlanRetriever(it's already in the enum but not sent)ListAndSetAggregateandHybridSearchSkipOrderByRewriteto the features stringReferences