Convert SQL Server CDC row data following upstream and expected type · Issue #21896 · risingwavelabs/risingwave · GitHub
More Web Proxy on the site http://driver.im/
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
Talked with @xiangjinwu offline, For SQL Server CDC, since a third-party library is used to read snapshots, the current schema check does not take into account the schema of the upstream table but only checks the converted schema.
This will cause some problems, such as the upstream Money type will be converted to i64, but we only have this i64 and cannot determine whether the i64 is the upstream i64 or the upstream Money type. We should use the upstream datatype, the intermediate data type, and the target data type to perform schema check. Currently, for this issue, the Money type has been specially judged as a hot fix.
The text was updated successfully, but these errors were encountered:
xiangjinwu
changed the title
Full schema validation for SQL Server CDC
Convert SQL Server CDC row data following upstream and expected type
May 16, 2025
Talked with @xiangjinwu offline, For SQL Server CDC, since a third-party library is used to read snapshots, the current schema check does not take into account the schema of the upstream table but only checks the converted schema.
This will cause some problems, such as the upstream Money type will be converted to i64, but we only have this i64 and cannot determine whether the i64 is the upstream i64 or the upstream Money type. We should use the upstream datatype, the intermediate data type, and the target data type to perform schema check. Currently, for this issue, the Money type has been specially judged as a hot fix.
The text was updated successfully, but these errors were encountered: