Why are Mismatch Columns and Skipped Updates set as Warning-level logs?

[wmcgee4]

Is there a reason this type of log is only a Warning-level log rather than an Error log?

[SOURCE_CAPTURE  ]W:  Mismatch number of columns in table AAA.BBBB: CDC event has XX columns while Replicate knows YY.

[SOURCE_CAPTURE  ]W:  Temporary column index XX in table 'AAAAA' has unknown size. Skipping updates.  (mysql_endpoint_capture.c:2561)

From our perspective, if Qlik does not have full knowledge of all the columns for a given table during replication and replication cannot be performed for all changes, then Qlik should error out on this.

We have seen the second type of logs in conjunction with the mismatch column issue and given data quality is paramount for us and our consumers, a skipped update is not acceptable and so we have had to create custom monitoring for these Warning logs.

[DesmondWOO]

Hi @wmcgee4 ,

I completely understand your concern. When the Replicate task reported the warning message, did it skip the update or suspend the table?

If updates were skipped, I would recommend creating a support ticket for further assistance.

Regards,
Desmond

[john_wang]

Besides Desmond comment: Please set SOURCE_CAPTURE to Verbose, re-create the behavior then upload the Diagnostics Package to the support ticket. And also please provide the source table creation DDL (include PK, Unique Index, compression ... all information).

BTW, do not forget to decrypt the newly generated task log file and upload it as well.

Thanks,

John.