-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Test and release per-stream state handling in Postgres Source #14457
Comments
Hey team! Please add your planning poker estimate with ZenHub @edgao @ryankfu @subodh1810 |
UPDATE: this ticket is mostly taken care of by the OSS platform team with acceptance tests from Lake and Benoit. I do need to provide an update to them on the create a connection with an older version of the Postgres source but I believe their tests currently cover that (not fully verified) I'm going to instead shift this ticket to address the documentation of the logic that was discovered as a result of spectating Benoit and Lake set up a per-stream non-CDC sync locally. I will update the ticket with a living google doc and tag the databases and oss-platform team once it's ready for review. Furthermore, I'm adding in a diagram of how our syncs work prior to |
OSS platform team merged the Additionally, will be documenting any issues with setup and testing within Postgres Source GA doc. Due note that the document is not visible to non-Airbyters while the team continues to work out any refinements in the setup and information sharing process Platform OSS filed issues related to
|
Document covering the per-stream changes here with overview of the complications, what is |
Once platform is ready with per-stream state, we need to manually test
Context:
The text was updated successfully, but these errors were encountered: