jtuglu1 commented on code in PR #19486: URL: https://github.com/apache/druid/pull/19486#discussion_r3276719499
########## docs/querying/query-context-reference.md: ########## @@ -71,7 +71,8 @@ Unless otherwise noted, the following parameters apply to all query types, and t |`setProcessingThreadNames`|`true`| Whether processing thread names will be set to `queryType_dataSource_intervals` while processing a query. This aids in interpreting thread dumps, and is on by default. Query overhead can be reduced slightly by setting this to `false`. This has a tiny effect in most scenarios, but can be meaningful in high-QPS, low-per-segment-processing-time scenarios. | |`sqlPlannerBloat`|`1000`|Calcite parameter which controls whether to merge two Project operators when inlining expressions causes complexity to increase. Implemented as a workaround to exception `There are not enough rules to produce a node with desired properties: convention=DRUID, sort=[]` thrown after rejecting the merge of two projects.| |`cloneQueryMode`|`excludeClones`| Indicates whether clone Historicals should be queried by brokers. Clone servers are created by the `cloneServers` Coordinator dynamic configuration. Possible values are `excludeClones`, `includeClones` and `preferClones`. `excludeClones` means that clone Historicals are not queried by the broker. `preferClones` indicates that when given a choice between the clone Historical and the original Historical which is being cloned, the broker chooses the clones. Historicals which are not involved in the cloning process will still be queried. `includeClones` means that broker queries any Historical without regarding clone status. This parameter only affects native queries. MSQ does not query Historicals directly.| -|`realtimeSegmentsOnly` |`false`| When set to true, only query realtime segments. Historical segments are excluded. | +|`realtimeSegmentsMode` |`include`| Controls which segments are queried, classified by whether a historical replica exists. `include` queries all segments. `exclusive` queries only segments served solely by realtime servers; any segment with at least one historical replica (including segments mid-handoff) is excluded. `exclude` is the inverse: segments served solely by realtime servers are skipped, but segments mid-handoff that have both a realtime and a historical replica are still queried. | Review Comment: Yeah this was overly verbose – I've trimmed it down. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
