zachjsh commented on code in PR #14319:
URL: https://github.com/apache/druid/pull/14319#discussion_r1202960376
##########
docs/configuration/index.md:
##########
@@ -1954,6 +1954,7 @@ The Druid SQL server is configured through the following
properties on the Broke
|`druid.sql.http.enable`|Whether to enable JSON over HTTP querying at
`/druid/v2/sql/`.|true|
|`druid.sql.planner.maxTopNLimit`|Maximum threshold for a [TopN
query](../querying/topnquery.md). Higher limits will be planned as [GroupBy
queries](../querying/groupbyquery.md) instead.|100000|
|`druid.sql.planner.metadataRefreshPeriod`|Throttle for metadata
refreshes.|PT1M|
+|`druid.sql.planner.metadataColumnTypeMergePolicy`|Defines how column types
will be chosen when faced with differences between segments when computing the
SQL schema. Options are specified as a JSON object, with valid choices of
`{"type":"leastRestrictive"}` or `{"type":"latestInterval"}`. For
`leastRestrictive`, Druid will automatically widen the type computed for the
schema to a type which data across all segments can be converted into, however
planned schema migrations can only take effect once all segments have been
re-ingested to the new schema. With `latestInterval`, the column type in most
recent time chunks defines the type for the schema.
|`{"type":"leastRestrictive"}`|
Review Comment:
Any reason to not just have this configured with more simple values like
`leastRestrictive` or `latestInterval`
--
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]
