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
I think we should make a push to get #8017 and #8041 knocked out soon, but just document the upstream bug (DBZ-3915) as a known limitation. @philip-stoev do you agree?
@benesch It will be a tortured "known limitation". Something like "stop all updates to the tables you intend to replicate to Mz until you have configured Debezium completely , all snapshots have been taken , plus 10 seconds"
@benesch It will be a tortured "known limitation". Something like "stop all updates to the tables you intend to replicate to Mz until you have configured Debezium completely , all snapshots have been taken , plus 10 seconds"
Yeah, I totally agree. I hope it is the kind of limitation that makes people reconsider using SQL Server + Debezium.
These are the three known bugs with our Debezium + Microsoft SQL Server integration:
DATETIMEOFFSET
from SQL Server is replicated asTEXT
#8017DATETIME2
values from SQL Server arrive asBIGINT
#8041I think we should make a push to get #8017 and #8041 knocked out soon, but just document the upstream bug (DBZ-3915) as a known limitation. @philip-stoev do you agree?
cc @nmeagan11 @umanwizard
The text was updated successfully, but these errors were encountered: