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
TiCDC Redo log files don't have version control, there is no file header to describe the version of file format and the compression algorithm used. This make the redo file is hard to extend. For example #10171 introduced LZ4 compression for redo file, but it depends on the hardcode LZ4 magic number to judge if this file is compressed or not. What if this file is not compressed but the first 4 bytes are accidentally match the hardcode LZ4 magic number?
The text was updated successfully, but these errors were encountered:
What is your question?
TiCDC Redo log files don't have version control, there is no file header to describe the version of file format and the compression algorithm used. This make the redo file is hard to extend. For example #10171 introduced LZ4 compression for redo file, but it depends on the hardcode LZ4 magic number to judge if this file is compressed or not. What if this file is not compressed but the first 4 bytes are accidentally match the hardcode LZ4 magic number?
The text was updated successfully, but these errors were encountered: