-
Notifications
You must be signed in to change notification settings - Fork 126
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
Druid Explore Exactify mode #4397
Conversation
// comparison toplist | ||
if !isTimeRangeNil(q.ComparisonTimeRange) { | ||
// execute toplist for base and get dim list | ||
// create and add filter and execute comprison toplist | ||
// remove strict limits in comp toplist sql | ||
if drivers.DialectDruid != olap.Dialect() || q.Exact { |
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'm worried about how inlined/nested/scattered this fix is since the comparison logic is already tricky to follow. I'm wondering if it could we moved into a separate branch of logic without altering the existing implementation too much? For example, something like this on line 117:
if olap.Dialect() == drivers.DialectDruid && !q.Exact {
return q.executeDruidApproximate(ctx, olap, mv, priority, security)
}
Benchmarks
|
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.
Approving and will address the outstanding comments in a follow up PR
* Druid Exactify * Druid Exactify * Druid Exactify * Druid Exactify * Druid Exactify --------- Co-authored-by: Egor Ryashin <egor.ryashin@rilldata.com>
No description provided.