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
Currently, TRUNCATE messages are ignored. This can provide unexpected behaviour because the stream will not capture all records which have been deleted by the operation.
Each truncate message, contains the number of rels (tables) being truncated in the same LSN. This is tricky because:
The truncate message does not carry the keys of each row which needs to be deleted
It all happens in the same LSN
Conduit only supports Snapshot, Create, Delete and Update operations. Truncate does not fit in any of these
Some systems ignore it, others (like dbz) have an additional truncate operation to handle this type of operation.
Since its introduction in 2008, TRUNCATE is an optional feature in SQL. However, other systems do support way to empty a collection entirely without bother to emit individual event per delete.
The least work involved here will be to warn/block/something so the user is aware this is happening.
The text was updated successfully, but these errors were encountered:
Feature description
Currently,
TRUNCATE
messages are ignored. This can provide unexpected behaviour because the stream will not capture all records which have been deleted by the operation.Each truncate message, contains the number of rels (tables) being truncated in the same LSN. This is tricky because:
Some systems ignore it, others (like dbz) have an additional
truncate
operation to handle this type of operation.Since its introduction in 2008,
TRUNCATE
is an optional feature in SQL. However, other systems do support way to empty a collection entirely without bother to emit individual event per delete.The least work involved here will be to warn/block/something so the user is aware this is happening.
The text was updated successfully, but these errors were encountered: