317brian commented on code in PR #17740:
URL: https://github.com/apache/druid/pull/17740#discussion_r1990202066


##########
docs/ingestion/ingestion-spec.md:
##########
@@ -243,7 +243,7 @@ Dimension objects can have the following components:
 
 | Field | Description | Default |
 |-------|-------------|---------|
-| type | Either `auto`, `string`, `long`, `float`, `double`, or `json`. For 
the `auto` type, Druid determines the most appropriate type for the dimension 
and assigns one of the following: STRING, ARRAY<STRING\>, LONG, ARRAY<LONG\>, 
DOUBLE, ARRAY<DOUBLE\>, or COMPLEX<json\> columns, all sharing a common 
'nested' format. When Druid infers the schema with schema auto-discovery, the 
type is `auto`. | `string` |
+| type | Either `auto`, `string`, `long`, `float`, `double`, or `json`. For 
the `auto` type, Druid determines the most appropriate type for the dimension 
and assigns one of the following: STRING, Array<String\>, LONG, ARRAY<LONG\>, 
DOUBLE, ARRAY<DOUBLE\>, or COMPLEX<json\> columns, all sharing a common 
'nested' format. When Druid infers the schema with schema auto-discovery, the 
type is `auto`. | `string` |

Review Comment:
   ```suggestion
   | type | Either `auto`, `string`, `long`, `float`, `double`, or `json`. For 
the `auto` type, Druid determines the most appropriate type for the dimension 
and assigns one of the following: STRING, ARRAY<String\>, LONG, ARRAY<LONG\>, 
DOUBLE, ARRAY<DOUBLE\>, or COMPLEX<json\> columns, all sharing a common 
'nested' format. When Druid infers the schema with schema auto-discovery, the 
type is `auto`. | `string` |
   ```



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