Closed eugen-korentsov closed 7 months ago
Maybe we should exclude the generated column, as CDC will not output generated column at all. cc @Lloyd-Pottiger
If CDC does not provide an option to exclude specified columns, then the only way is to exclude the generated columns. Agree with @breezewish If it is possible to ignore columns in CDC, then it might make sense to add an option to tidb2dw as a parameter to exclude columns. For example, tidb2dw --ignore-columns ref_normalized, other_column, etc.
Hello guys :) Also, I have faced with the same problem for generated column types as @eugen-korentsov described above. I will be so grateful if you can find the solution how to fix this limitation as soon as possible. Because it is the biggest pitfall for my project now.
For now, bigquery flag --allow_jagged_rows or gcsRef.AllowJaggedRows = true in pkg/bigquerysql/operation.go helped, it just adding null value into generated column.
fixed by ce3ed47e0eb495ff01ecc6fb7dda5a7cb3bd12ba
How to reproduce:
Run tidb2dw for this table, as result:
csv:
so no generated column present in csv. I tried using both stored and virtual options, but unfortunately, neither of them worked.