-
Notifications
You must be signed in to change notification settings - Fork 10
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
fix: Use airbyte state message format + tracking. #18
Conversation
This change will fix incremental extraction for a few TAPs, like tap-amplitude and tap-s3. - Adds a new entry to state tracking json, 'airbyte_state'. - This new entry is populated on any invocation, and contains airbyte's way to track state as documented here: https://docs.airbyte.com/understanding-airbyte/database-data-catalog. - If this entry does not exist, we fallback to what was originally being done. - If this entry does exist, we use this data as the input state.json to airbyte's docker container.
@z3z1ma let me know if you have any questions on this PR |
@edgarrmondragon could you help getting the right pair of eyes on this? |
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 wonder if @SpaceCondor is affected by this or that this change at least doesn't break things for him
Co-authored-by: Edgar Ramírez Mondragón <[email protected]>
@JichaoS @arianeschang In the interesting of unblocking y'all I'm gonna merge this |
This change will fix incremental extraction for a few TAPs, like tap-amplitude and tap-s3.