-
Notifications
You must be signed in to change notification settings - Fork 328
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
Push down IN filter #4958
Comments
I think this feature should be supported if
Simple I'm interested in this issue, but this feature seems to be a high priority(marked as v0.11). |
I also did some research on this earlier. I tried 2 sqls:
And I found the key difference between these two when optimizing is when it comes to
It seems for some reason |
I think this is because I tried changing CREATE TABLE monitor (
host STRING,
ts TIMESTAMP DEFAULT CURRENT_TIMESTAMP() TIME INDEX,
cpu FLOAT64 DEFAULT 0,
memory FLOAT64,
PRIMARY KEY(host));
INSERT INTO monitor
VALUES
("127.0.0.1", 1702433141000, 0.5, 0.2),
("127.0.0.2", 1702433141000, 0.3, 0.1),
("127.0.0.1", 1702433146000, 0.3, 0.2),
("127.0.0.2", 1702433146000, 0.2, 0.4),
("127.0.0.1", 1702433151000, 0.4, 0.3),
("127.0.0.2", 1702433151000, 0.2, 0.4);
explain analyze select host from monitor where host in ("127.0.0.1") limit 1;
In the above plans, current behavior
|
I try to submit a PR. |
What type of enhancement is this?
Performance
What does the enhancement do?
In pushdown is not supported
Standalone log
Implementation challenges
No response
The text was updated successfully, but these errors were encountered: