-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Wire up SELECT DISTINCT #2568
Wire up SELECT DISTINCT #2568
Conversation
Looks good so far. Although your sort doesn't handle a Curious how you're going to handle it when they pass in a tag name and a |
Fixes #1815 |
2ae20cf
to
fbc59ab
Compare
|
||
return other | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would simplify this method to look like this... https://gist.github.com/dgnorton/3125e459045a5cedc948
I agree with @jwilder that the |
Need to add more tests for the validation code. e.g. |
Addressed all items. Will address |
b263117
to
fc7d63c
Compare
LGTM 👍 |
Looks good. One thing left over from this is to handle when the user passes in a tag key to distinct. Logged #2612 |
Distinct with strings
the raw data
distinct with no where or group by
Distinct with no fields will currently return an error (not supported)
Distinct with more than one field will currently return an error (not supported)
Distinct with a group by and no where clause will err out (like all aggregate functions should)
Distinct with group by and where should bucket values appropriatly
Distinct with numeric data
the raw data
distinct with no where or group by
distinct with different groupings