or we assume that we support all of sync modes right now?

yes or we base it on if the destination has normalization enabled or not

Well FE doesn’t know whether it supports normalization or not. So should we assume that all 3 modes for destination are supported then?

in the FE, you don’t check if destination has

supportsIncremental

in their specs to

true

in order to set incremental on the source/sync too?

No. We have a field supportedSyncModes and it returns them.

Ok, so the BE would need to add some

destinationSupportedSyncMode

on the connection objects or somewhere to inform what’s possible or not with this combination of source/destination connectors

let me just clarify 1 thing: so from frontend we send syncMode and destinationSyncmode, but as we have 1 one dropdown we are actually selecting 2 enums, thats why I need to know all possible mappings we support. According to what Charles posted, we want to display full_refresh -> overwrite, incremental -> append, incremental -> append_dedup. Theoretically we should have cartesian product of this modes displayed, but I and Charles decided that we have only 3 now. so we should have then

full_refresh append

and

incremental overwrite

too?

Just adding

full_refresh append

because we have a user case from a user not

incremental overwrite

because we’re not sure if that’s useful yet

Ok. Sure

Thanks!