-
Notifications
You must be signed in to change notification settings - Fork 41
Description
I use Tuple Sketches on my datasource and as such I need to use the appropriate aggregation on the query. Those aggregations are not available on the query builder, so it looks like the JSON option would allow me to write the entire query by hand since it is using something that the query builder doesn't know about.
But then, the JSON query is parsed only for known aggregation types. This makes absolutely no sense.
Druid supports plugins, if I create a new interleaveDigits aggregation I should be able to use it. The go-druid library can't possibly know about every Druid extension both public and private in every company.
The JSON queries should just be interpolated with the interval variables and sent to Druid without going through the builder at all or, if go-druid actually aims to be compatible with everything, it should accept any unknown aggregation and post aggregation as a map[string]any instead of returning an error.