-
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
GroupByQuery on PostAggregation #1292
Conversation
763ef8b
to
63f4b64
Compare
// add an extra layer of merging, simulate broker forwarding query to historical | ||
TestHelper.assertExpectedObjects( | ||
expectedResults, | ||
factory.getToolchest().mergeResults(mergedRunner).run(fullQuery, context), |
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.
Can you decorate the runner with the pre merge and post merge decorators from the toolchest?
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.
Fixed!
Thanks for the bug tracking and PR @guobingkun ! |
63f4b64
to
26f9ad6
Compare
…avingSpec is still applied on postAggregations which are removed in the forwarded query. Add a unit test to replicate the issue. Add a query that can replicate this issue into integration test.
26f9ad6
to
cf155e4
Compare
👍 |
@guobingkun : Could you please fill out the appropriate CLA at http://druid.io/community/cla.html ? |
Hi @drcrallen , I think I filed one already sometime yesterday? |
Yep, I see it now, thanks! |
@drcrallen Fwiw, I'm not sure which CLA you are believing that Bingkun has filled out, but he was added a while back to our corporate CLA. |
Actually, no, he's apparently not covered yet. Need to correct that. |
@cheddar @guobingkun filled out the individual CLA. He wasn't covered on the corporate CLA and we can't always tell which company someone is from :) |
This patch aims to fix an issue that after Broker forwards GroupByQuery to Historical, "havingSpec" is still applied on PostAggregations. Since PostAggregations are removed from the forwarded query, "havingSpec" will likely evaluate to false on Historical in this case.
Here is a groupBy query that could replicate this issue on wikipedia local index data,
When this query is sent to Broker, an empty set is returned.
Expected result is
Send the same query directly to Historical will return the expected result.