-
Notifications
You must be signed in to change notification settings - Fork 110
Use journal table v2 as default #3921
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
base: main
Are you sure you want to change the base?
Use journal table v2 as default #3921
Conversation
…ice invocation ingestion logic to write the journal v2
… and then tries to read from journal table v1
443e68d to
257c1d9
Compare
|
This is ready for an initial pass. The test is failing because i still didn't figure out how to do the exclusion properly 🫨 but the exclusion is legit |
…tever reason the negotiated protocol when invoking will be less than 4.
…he problematic situations. Fix some incorrectly handled corner cases, such as deletion of journal when the pinned deployment is not set yet.
…tion. See the changes for more details.
257c1d9 to
60b2632
Compare
|
|
This case can happen if we got an invocation scheduled (or inboxed) before the journal v2 default feature was enabled.
|
Fixed the problem with exclusions! |
|
did some manual testing locally, primarily around scheduled invocations, first disabling then enabling, and viceversa. So far everything seems to work as expected. |
Part of #3184