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
Add support for partition-local stores #1514
Conversation
642bdc7
to
2e63458
Compare
2e63458
to
0a62112
Compare
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.
This is great. I like the approach you're taking for this one, it's a good mix of flexible and minimally invasive. 🚀
I think extending vast.fbs.partition.v0
is the way to go, so these two commits can probably be squashed into one in the end. I also left some in-line comments.
0184d24
to
95e05bb
Compare
95e05bb
to
e4de9f9
Compare
b8a3b31
to
d87fce0
Compare
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.
reviewed with @dominiklohmann.
d87fce0
to
389f5e3
Compare
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.
Reviewed the last two commits, they mirror exactly what we talked about in the last review.
389f5e3
to
cb5404f
Compare
The explorer needs this to deduplicate the events from multiple second-stage queries.
This reverts commit d287261.
This reverts commit 3930047.
This allows us to use query as a strongly typed object that doesn't need any additional context. The `weak_actor_pointer`s are not used any more and will be removed from the actor interfaces in the next commit.
b6fd917
to
64d733d
Compare
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.
Just some minor code nits. This is looking really good now.
Doing some final regression testing locally before approving.
Co-authored-by: Dominik Lohmann <mail@dominiklohmann.de>
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.
Aside from the count
performance regression while imports are running this is looking good. Looks like it'll be exactly 42 commits after all.
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.
Performance is looking much better now while imports are running. IMO, this is ready to ship. 🚀
The hits for `#type` and `#field` extractors will always be exact, so there is no need to double check. This does not apply to continuous exports, because the candidate check is the sole filter in that case.
📔 Description
This refactoring changes the protocol for the output path.
The EXPORTER is not an archive client any more but only talks to the index.
📝 Checklist
🎯 Review Instructions
By commit.