-
Notifications
You must be signed in to change notification settings - Fork 276
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
[Feature]: Zonemap Eval Optimization EvaluateFilterByZoneMap is too slow #10273
Comments
Changed into a feature, because need to work out design. |
目前的zonemap eval无法和普通的expr一样转成一个pipeline expr,然后复用这个pipeline expr eval,需要想办法做到和普通的expr一样。 |
@nnsgmsone Why to handle zonemap evaluation using pipeline expr logic? What's the problem of previous approach? |
@fengttt please confirm who can be the owner and caculate plan dates. |
以前的逻辑不能处理函数。 @aunjgr ,比如最简单的cast函数 |
@aunjgr I think @XuPeng-SH may did some fast path work with zonemap. Please sync with him and let me know if we should close this one. |
Zonemap evaluation is largely improved. This can be closed. |
Is there an existing issue for the same bug?
Environment
Actual Behavior
Zonemap eval overhead is huge. See profiling
It is not clear to me what we should do. There need to be a design, but we must fix ths.
Expected Behavior
No response
Steps to Reproduce
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: