[druid] branch master updated: Add useNativeQueryExplain in sql query context documentation (#12924) (#12934)

[ab...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

abhishek pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/druid.git


The following commit(s) were added to refs/heads/master by this push:
     new 6fec1d4c95 Add useNativeQueryExplain in sql query context documentation (#12924) (#12934)
6fec1d4c95 is described below

commit 6fec1d4c95a93b14e334b5fe8713408f4ebc1f0e
Author: Petar Petrov <Mi...@users.noreply.github.com>
AuthorDate: Mon Aug 22 11:01:15 2022 +0000

    Add useNativeQueryExplain in sql query context documentation (#12924) (#12934)
    
    Co-authored-by: Petar Petrov <pe...@system73.com>
---
 docs/querying/sql-query-context.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/querying/sql-query-context.md b/docs/querying/sql-query-context.md
index db5350d9f1..6b7a746623 100644
--- a/docs/querying/sql-query-context.md
+++ b/docs/querying/sql-query-context.md
@@ -42,6 +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)|
 
 ## Setting the query context
 The query context parameters can be specified as a "context" object in the [JSON API](sql-api.md) or as a [JDBC connection properties object](sql-jdbc.md).
@@ -72,4 +73,3 @@ try (Connection connection = DriverManager.getConnection(url, connectionProperti
   // create and execute statements, process result sets, etc
 }
 ```
-


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org