paul-rogers commented on issue #12546: URL: https://github.com/apache/druid/issues/12546#issuecomment-1196206678
@clint, you also asked about SQL mapping. My suggestion is to enforce a limited set of types: `VARCHAR`, `BIGINT`, `FLOAT` and `DOUBLE`, which directly correspond to the Druid storage types. (Other types can be intermediate values.) This way, if Druid were ever to support a 1-byte integer value, we could use `TINYINT` (or `BOOLEAN`) to label that type. If we mapped `TINYINT` to `long` internally, then we'd have an ambiguous mess later on. We've already got the beginnings of ambiguity with `TIMESTAMP`: it has a meaning in SQL, but we just work with it as a `long`. SQL does require rigor in the type system to keep everything straight. -- 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]
