vogievetsky commented on code in PR #16849:
URL: https://github.com/apache/druid/pull/16849#discussion_r1727956216


##########
docs/ingestion/ingestion-spec.md:
##########
@@ -232,7 +232,7 @@ A `dimensionsSpec` can have the following components:
 | `spatialDimensions`    | An array of [spatial 
dimensions](../querying/geo.md).                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                            | `[]`    |
 | `includeAllDimensions` | Note that this field only applies to string-based 
schema discovery where Druid ingests dimensions it discovers as strings. This 
is different from schema auto-discovery where Druid infers the type for data. 
You can set `includeAllDimensions` to true to ingest both explicit dimensions 
in the `dimensions` field and other dimensions that the ingestion task 
discovers from input data. In this case, the explicit dimensions will appear 
first in the order that you specify them, and the dimensions dynamically 
discovered will come after. This flag can be useful especially with auto schema 
discovery using [`flattenSpec`](./data-formats.md#flattenspec). If this is not 
set and the `dimensions` field is not empty, Druid will ingest only explicit 
dimensions. If this is not set and the `dimensions` field is empty, all 
discovered dimensions will be ingested. | false   |
 | `useSchemaDiscovery` | Configure Druid to use schema auto-discovery to 
discover some or all of the dimensions and types for your data. For any 
dimensions that aren't a uniform type, Druid ingests them as JSON. You can use 
this for native batch or streaming ingestion.  | false  | 
-
+| `forceSegmentSortByTime` | When set to true (the default), segments created 
by the ingestion job are sorted by `{__time, dimensions[0], dimensions[1], 
...}`. When set to false, segments created by the ingestion job are sorted by 
`{dimensions[0], dimensions[1], ...}`. To include `__time` in the sort order 
when this parameter is set to `false`, you must include a dimension named 
`__time` with type `long` explicitly in the `dimensions` list.<br /><br 
/>Setting this to `false` is an experimental feature; see 
[Sorting](partitioning.md#sorting) for details. | `false` |

Review Comment:
   You need to update the default (3rd column) to `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