You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a check (#14599 / #14519) when migrating syncs to per-stream state that ensures that every enabled stream has state before migrating. However, this check should only happen for incremental streams
The text was updated successfully, but these errors were encountered:
I don't think this ticket is necessary. The validation only checks if the state that was produced at the end of the sync has states for all streams in the catalog, before it writes that state to the database. So this shouldn't matter if a sync had ran before or not
evantahler
changed the title
Do not prevent migration to per-stream state for syncs that have never run
Only validate that incremental streams have state before migrating connection from legacy to per-stream state
Jul 22, 2022
evantahler
changed the title
Only validate that incremental streams have state before migrating connection from legacy to per-stream state
Only validate that incremental streams have state before migrating connection to per-stream
Jul 22, 2022
We have a check (#14599 / #14519) when migrating syncs to per-stream state that ensures that every enabled stream has state before migrating. However, this check should only happen for incremental streams
The text was updated successfully, but these errors were encountered: