-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsupported aggregation type on JSON query #145
Comments
Hello @Fryuni |
Some aggregations are only available on the native JSON query, like those for Tuple Sketches
I can make the backend support arbitrary aggregations from the JSON editor, but the frontend builder is a complete mystery for me. But I can try. I'll start with a PR on |
@jbguerraz I opened the PR on the library: grafadruid/go-druid#83 |
and merged @Fryuni ! :) thx a lot! |
Great, so updating the library here should already enable custom queries. |
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. Thego-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 amap[string]any
instead of returning an error.The text was updated successfully, but these errors were encountered: