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.

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

Lookup limit push down #2796

Merged

Conversation

bright-starry-sky
Copy link
Contributor

No description provided.

@bright-starry-sky bright-starry-sky added the wip Solution: work in progress label Sep 6, 2021
@Shylock-Hg
Copy link
Contributor

And you should add a test case.

@bright-starry-sky bright-starry-sky added ready-for-testing PR: ready for the CI test and removed wip Solution: work in progress labels Sep 9, 2021
@bright-starry-sky bright-starry-sky changed the title [DRAFT] lookup limit push down Lookup limit push down Sep 9, 2021
@bright-starry-sky
Copy link
Contributor Author

Addressed comments.

@bright-starry-sky
Copy link
Contributor Author

Related #2602

panda-sheep
panda-sheep previously approved these changes Sep 14, 2021
Copy link
Contributor

@panda-sheep panda-sheep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job!

src/clients/storage/GraphStorageClient.cpp Show resolved Hide resolved
src/storage/index/LookupBaseProcessor.h Show resolved Hide resolved
@bright-starry-sky
Copy link
Contributor Author

Corrected comments. thanks @panda-sheep

panda-sheep
panda-sheep previously approved these changes Sep 14, 2021
@bright-starry-sky
Copy link
Contributor Author

rebase and resolve conflict

Copy link
Contributor

@critical27 critical27 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally LGTM, wait graph PR is ready.

@bright-starry-sky bright-starry-sky merged commit dbea9c7 into vesoft-inc:master Sep 15, 2021
@bright-starry-sky bright-starry-sky deleted the push_dowm_limit_sample branch September 15, 2021 01:37
@bright-starry-sky
Copy link
Contributor Author

related #2823

@cangfengzhs
Copy link
Contributor

The limit must be the top node of the execution plan, otherwise the size of the final dataset will be smaller than the limit count due to the filter (and possibly dedup) discarding part of the data.

@Shylock-Hg
Copy link
Contributor

The limit must be the top node of the execution plan, otherwise the size of the final dataset will be smaller than the limit count due to the filter (and possibly dedup) discarding part of the data.

Yes the limit push down can't over the filter operation.

@bright-starry-sky
Copy link
Contributor Author

The limit must be the top node of the execution plan, otherwise the size of the final dataset will be smaller than the limit count due to the filter (and possibly dedup) discarding part of the data.

Good point. Thanks for your remind.
The limit can't cover filter, ttl and dedup. I'll deal with it later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-testing PR: ready for the CI test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants