Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Pull filter push down as a separate optimization #768

Closed
andyfengHKU opened this issue Sep 5, 2022 · 1 comment
Closed

Pull filter push down as a separate optimization #768

andyfengHKU opened this issue Sep 5, 2022 · 1 comment
Assignees
@andyfengHKU

Comments

@andyfengHKU
Copy link
Contributor

Currently whenever a node/rel table is scanned, we first apply filter (which is actually filter push down) and then apply property scans. This is not easy to read and ideally we should pull this optimization out and do property reading before filter.
@andyfengHKU andyfengHKU self-assigned this Sep 5, 2022
@ray6080 ray6080 removed the refactor label Jan 29, 2023
@andyfengHKU
Copy link
Contributor Author

Solved in #1397

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andyfengHKU andyfengHKU

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ray6080 @andyfengHKU