View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004185 | SymmetricDS | Bug | public | 2019-12-05 17:55 | 2019-12-09 17:27 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.11.0 | ||||
| Target Version | 3.11.2 | Fixed in Version | 3.11.2 | ||
| Summary | 0004185: Incorrect resolver behavior: Failed to find and delete the blocking row | ||||
| Description | Incorrect resolver behavior when two conflicts occur in the same batch and the second conflict is caused by an UPDATE that affects zero rows. ERROR [client-1] [DefaultDatabaseWriterConflictResolver] [client-1-dataloader-22] Failed to find and delete the blocking row by primary key: DELETE from "DB"."PUBLIC"."MYTEST" where "ID" = ? {2} For example, a batch that contains an INSERT for a row that already exists, followed by an UPDATE to a row that does not exist. The first conflict gets an exception, but the exception is not cleared from memory. On the second conflict, there is no exception from the database, so it incorrectly uses the first exception to determine its behavior. | ||||
| Additional Information | Even with the ugly error message in the log, the data does still manage to get synced correctly. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-12-05 17:55 | elong | New Issue | |
| 2019-12-05 17:55 | elong | Status | new => assigned |
| 2019-12-05 17:55 | elong | Assigned To | => elong |
| 2019-12-05 17:55 | elong | Issue generated from: 0004184 | |
| 2019-12-05 17:55 | elong | Relationship added | related to 0004184 |
| 2019-12-05 18:06 | elong | Status | assigned => resolved |
| 2019-12-05 18:06 | elong | Resolution | open => fixed |
| 2019-12-05 18:06 | elong | Fixed in Version | => 3.11.2 |
| 2019-12-09 17:27 | admin | Status | resolved => closed |