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
As part of #2337, we would like to introduce a new configuration enum for sync modes on the destination side.
Depending on the configuration of the AirbyteCatalog in #2370, destinations should not rely on sync_mode anymore (reserved for sources)
Describe the solution you’d like
Destinations should depend on destination_sync_mode instead to determine if the data in the destination should be overwritten or appended to in the _airbyte_raw tables.
Describe the alternative you’ve considered or used
Destinations can still work in the meantime with the sync_mode from sources as before but then you can't specify full refresh append for example.
The text was updated successfully, but these errors were encountered:
Since this PR introduces destination connectors that require destination sync modes to be defined, I will wait until the PR for the front-end (#2371) is ready before merging this one (#2460) to master.
Otherwise, newly created sync will be failing since the UI won't be setting/defining destination sync modes yet
Tell us about the problem you're trying to solve
As part of #2337, we would like to introduce a new configuration enum for sync modes on the destination side.
Depending on the configuration of the AirbyteCatalog in #2370, destinations should not rely on
sync_mode
anymore (reserved for sources)Describe the solution you’d like
Destinations should depend on
destination_sync_mode
instead to determine if the data in the destination should be overwritten or appended to in the _airbyte_raw tables.Describe the alternative you’ve considered or used
Destinations can still work in the meantime with the sync_mode from sources as before but then you can't specify full refresh append for example.
The text was updated successfully, but these errors were encountered: