debezium / debezium/dbz

SQL Server connector produces the same record during snapshot and streaming [DBZ-3375]

Open
#448 0 comments 0 reactions 1 assignee Claimed by @jpechane View on GitHub
component/sqlserver-connector migrated-from-jira type/bug
Dominant language
HTML
Stars
6
Forks
9
Avg merge
2d 19h
Merged PRs (30d)
1

Description

Migrated from [DBZ-3375](https://issues.redhat.com/browse/DBZ-3375)

The issue was originally discovered while working on DBZ-2975: we've got some test suites reworked to test multiple databases being processed per task, and some of them started failing due to unexpected messages being produced:
# {{SQLServerConnectorIT#testTableExcludeList}}
# {{SQLServerConnectorIT#testBlacklistTable}}

We managed to reproduce the failures on the original codebase by adding extra assertions. Please see the reproduction details in [https://github.com/debezium/debezium/pull/2280].

One of the newly added assertions in each test fails with the following error:
{quote}SqlServerConnectorIT.testBlacklistTable:961 expected:<1[0]> but was:<1[]>
SqlServerConnectorIT.testTableExcludeList:1005 expected:<1[0]> but was:<1[]>
{quote}
The tests above should stream 5 rows of id's 10-14 but occasionally record with id 1 is seen twice: once in the snapshot record returned and again in the streaming records.

This issue is reproduced inconsistently likely to a race condition.  
 

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.