Do we need overrideAttributes in DataCube?

We need to investigate all common scenarios where overrideAttribute could be used.

Feel free to comment if you use this in your case. @l2dy @alexbusu @cedrics @michalmisiewicz

[mkuthan]

That’s clear, the introspection sometimes returns non-optimal results, sometimes incorrect results and Turnilo must be able to override them. The question is how to configure and implement overriding strategy in consistent and easy to understand manner?

For example:

• use “kind” not only for UI modification but also for Druid query customisation
• if “kind” is not provided, type from introspection is used
• because there is no “Boolean” type in Druid, kind “Boolean” should me mapped into Druid String type
• I don’t know how to handle kind “Number” because there is more than one numeric type in Druid
• As long as there is no “kind” for measures it has to be added
• I don’t know how to handle histograms and uniques, Turnilo discovers the type from Plywood formula
• Finally there is also “native” cluster (wikipedia example) without any introspection 😃

[cedrics]

We’re using attributeOverrides when we ingest numeric values as string in order to have index on it. It would be great if we could remove attributeOverrides section from configuration and infer attributeOverrides for plywood based on dimension kind.

We use overrides for the same reason