santosh-d3vpl3x commented on code in PR #12936:
URL: https://github.com/apache/druid/pull/12936#discussion_r951924166


##########
docs/querying/sql-query-context.md:
##########
@@ -42,7 +42,7 @@ Configure Druid SQL query planning using the parameters in 
the table below.
 |`useGroupingSetForExactDistinct`|Whether to use grouping sets to execute 
queries with multiple exact distinct 
aggregations.|druid.sql.planner.useGroupingSetForExactDistinct on the Broker 
(default: false)|
 |`useApproximateTopN`|Whether to use approximate [TopN queries](topnquery.md) 
when a SQL query could be expressed as such. If false, exact [GroupBy 
queries](groupbyquery.md) will be used 
instead.|druid.sql.planner.useApproximateTopN on the Broker (default: true)|
 |`enableTimeBoundaryPlanning`|If true, SQL queries will get converted to 
TimeBoundary queries wherever possible. TimeBoundary queries are very efficient 
for min-max calculation on __time column in a datasource 
|druid.query.default.context.enableTimeBoundaryPlanning on the Broker (default: 
false)|
-|`useNativeQueryExplain`|If true, `EXPLAIN PLAN FOR` will return the explain 
plan as a JSON representation of equivalent native query(s), else it will 
return the original version of explain plan generated by 
Calcite.|druid.sql.planner.useNativeQueryExplain on the Broker (default: False)|
+|`useNativeQueryExplain`|If true, `EXPLAIN PLAN FOR` will return the explain 
plan as a JSON representation of equivalent native query(s), else it will 
return the original version of explain plan generated by 
Calcite.|druid.sql.planner.useNativeQueryExplain on the Broker (default: true)|

Review Comment:
   ```suggestion
   |`useNativeQueryExplain`|If true, `EXPLAIN PLAN FOR` will return the explain 
plan as a JSON representation of equivalent native query(s), else it will 
return the original version of explain plan generated by 
Calcite.|`druid.sql.planner.useNativeQueryExplain` on the Broker (default: 
true)|
   ```



-- 
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]

Reply via email to