[GitHub] [druid] jihoonson commented on a change in pull request #9545: SQL support for joins on subqueries.

[GitBox <gi...@apache.org>]

jihoonson commented on a change in pull request #9545: SQL support for joins on subqueries.
URL: https://github.com/apache/druid/pull/9545#discussion_r395793396
 
 

 ##########
 File path: docs/configuration/index.md
 ##########
 @@ -1632,6 +1632,10 @@ The Druid SQL server is configured through the following properties on the Broke
 |`druid.sql.planner.sqlTimeZone`|Sets the default time zone for the server, which will affect how time functions and timestamp literals behave. Should be a time zone name like "America/Los_Angeles" or offset like "-08:00".|UTC|
 |`druid.sql.planner.serializeComplexValues`|Whether to serialize "complex" output values, false will return the class name instead of the serialized value.|true|
 
+> Previous versions of Druid had properties named `druid.sql.planner.maxQueryCount` and `druid.sql.planner.maxSemiJoinRowsInMemory`.
+> These properties are no longer available. Since Druid 0.18.0, you can use `druid.server.http.maxSubqueryRows` to control the maximum
+> number of rows permitted across all subqueries.
 
 Review comment:
   Should `maxSubqueryRows` be added to the above table instead of `maxQueryCount` and `maxSemiJoinRowsInMemory`?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

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