techdocsmith commented on a change in pull request #11895:
URL: https://github.com/apache/druid/pull/11895#discussion_r745922925
##########
File path: docs/querying/segmentmetadataquery.md
##########
@@ -87,9 +87,11 @@ The format of the result is:
} ]
```
-Dimension columns will have type `STRING`, `FLOAT`, `DOUBLE`, or `LONG`.
-Metric columns will have type `FLOAT`, `DOUBLE`, or `LONG`, or the name of the
underlying complex type such as `hyperUnique` in case of COMPLEX metric.
-Timestamp column will have type `LONG`.
+All columns contain a `typeSignature` that Druid uses to represent the column
type information internally. The `typeSignature` is typically the same value
used to identify the JSON type information at query or ingest time. One of:
`STRING`, `FLOAT`, `DOUBLE`, `LONG`, or `COMPLEX<typeName>`, e.g.
`COMPLEX<hyperUnique>`.
+
+Columns will also have a legacy `type` name. For some column types, the value
may match the `typeSignature` (`STRING`, `FLOAT`, `DOUBLE`, or `LONG`). For
`COMPLEX` columns, the `type` only contains the name of the underlying complex
type such as `hyperUnique`.
Review comment:
```suggestion
Columns also have a legacy `type` name. For some column types, the value may
match the `typeSignature` (`STRING`, `FLOAT`, `DOUBLE`, or `LONG`). For
`COMPLEX` columns, the `type` only contains the name of the underlying complex
type such as `hyperUnique`.
```
nit. avoid future
--
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]
