-
Notifications
You must be signed in to change notification settings - Fork 13.9k
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
[Bugfix] Single Druid dimension spec error (part 2) #3920
[Bugfix] Single Druid dimension spec error (part 2) #3920
Conversation
This fix works for me, thanks, @Mogball. |
@fabianmenges touched this last, any comments? But there's a history of tweaks around edge cases here... The PR seems right as we should end the |
I can bring some light into this. TopN queries in Druid are much faster than groupBy queries, which is why if you could use either one, your definitely want to use
The much better performance and the broad use case of |
Wasn't aware of that. Thanks ms for the info! |
fixes #3943 |
I just pulled in this change and found that if you don't have a dimension in the group by, it will throw an exception.
|
issue: #3908
As a follow up to #3796, where I forgot to change the condition on the second branch, which is just an
else
now.Curious, why is there a branch to specifically handle a single dimension (which can't be a spec), with no
having_filters
andorder_desc = True
?