Remove timestamp limitation for MS SQL Server sinks
Answered
If a target database table has a column with the type "timestamp", it will fail on the first update. It seems like the update process is based on updating with the existing values, and just replacing the incoming ones. The timestamp type is a special type and cannot be updated with a value (it is a server generated value based on changes to the other columns). This means that all update attempts by Sesam will fail.
Note, that if the blacklist of the sink was respected during updates, it could be used to solve this issue.
-
Official comment
A workaround might be to write into a separate table and then use triggers, or alternatively have a writable view on top of the existing table. Another alternative would to use DTL to fill in the default values. And you can always write a custom microservice.
Comment actions
Please sign in to leave a comment.
Comments
1 comment