Apache Druid

In relation to this, “boolean” is also converted to “VARCHAR”. I think that’s not a correct behavior.

If implicit conversion supposed to happen, “boolean” should have been automatically converted to “long”.

Is this still true?

&gt; Druid natively supports five basic column types: “long” (64 bit signed int), “float” (32 bit float), “double” (64 bit float) “string” (UTF-8 encoded strings and string arrays), and “complex” (catch-all for more exotic data types like json, hyperUnique, and approxHistogram columns).

wow, strange! Thankfully this is not an issue with SQL based ingestion

I am sure this was unintentional, I think it's a side-effect of the fact that `defaultImpl` (with jackson deserialization) is the devil. i bet we can fix it by removing `defaultImpl` from something or other, and possibly adding a deserializer for back-compat if needed

It's possible the one on `DimensionSchema` is the one you are referring to