Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat(eap): Mutations consumer MVP #6216
feat(eap): Mutations consumer MVP #6216
Changes from 9 commits
c0b4e41
43d0acf
0bbe5cf
1234df0
f4c66ad
59d0836
97d1768
a75ee46
ce103b5
46a333a
b098710
7cd2a05
40278fd
ef36388
1d73a94
941d5db
c8ab36b
105d6d6
c2683fa
92ddabe
843e3bb
d6ea56b
2a71970
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
TODO: Write cancellation rows
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.
@untitaker 2 thoughts on this query:
We can rewrite this to avoid JOIN by using the WITH context. We would need to look into the performance differences.
What if we tried a UNION to get both the cancellation and the update in this one query? (SELECT ... UNION SELECT ...)
I'm also wondering if there's a way to do something like INSERT INTO ... VALUES (SELECT ...) (SELECT ...) so we can have 2 insertions back to back?
Just some thoughts -- I can try these out on some local data
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.
I think WITH conflicts directly with input() in my tests. I was also trying to use WITH to make the cancellation rows happen (using both WITH and UNION ALL). I'm not sure how it would help to avoid the join?
If you have a specific query let's discuss 1:1 or just push it, if it works already.
then we should just merge those MutationBatches at JSON level, I don't think the query needs to adapt to accomodate larger batches.