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
why should the downstream turn off the ttl_enable option ?
It is a discussed conclusion with @SunRunAway . I think the main reason is the upstream will also sync delete operations to the downstream so we do not need to open TTL in the downstream. Another reason is that if TTL_ENABLE is on in the downstream cluster, there can be true that a row is deleted in the downstream but still exists in the upstream because of the downstream's TTL job. To avoid some confusing phenomenon, it's better to turn it off
Is your feature request related to a problem?
CDC should support TTL table
Describe the feature you'd like
When a table is a TTL table in upstream, the downstream should turn off its
TTL_ENABLE
option toOFF
Describe alternatives you've considered
No response
Teachability, Documentation, Adoption, Migration Strategy
No response
The text was updated successfully, but these errors were encountered: