View Issue Details

IDProjectCategoryView StatusLast Update
0006173SymmetricDSImprovementpublic2024-01-09 16:18
Reporterelong Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.14.0 
Target Version3.14.12Fixed in Version3.14.12 
Summary0006173: Could not find trigger history, causes error of had X columns but expected Y
DescriptionWhen extracting a batch, if a trigger history cannot be found, it will look up and use the first active trigger history for the table. If the table was recently altered to include more or fewer columns, then the trigger history won't match the data, which leads to the following log messages and error:

WARN [node-1] [DataService] [node-1-dataextractor-1] Could not find trigger history 377 for table mytable for data_id 175848. Using trigger hist 1206 instead.
WARN [node-1] [DataExtractorService] node-1-push-default-1] The batch server01-10670 appears corrupt in staging, so removing it. (The extracted row for table mytable had 14 columns but expected 17. Corrupted row for data ID 175848

Instead, it should look up any active or non-active trigger history with a column count and primary key count that matches the data row. If there isn't a matching one, then there is no choice left but to use the current active trigger history.
Tagsextract

Relationships

related to 0006174 closedelong Could not find trigger history, causes error of had X columns but expected Y 

Activities

There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.14 f7e44073

2024-01-03 17:10:17

admin

Details Diff
0006173: Could not find trigger history, causes error of had X columns
but expected Y
Affected Issues
0006173
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/DataService.java Diff File

SymmetricDS: 3.15 f70233d4

2024-01-03 17:10:17

admin

Details Diff
0006173: Could not find trigger history, causes error of had X columns
but expected Y
Affected Issues
0006173
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/DataService.java Diff File

Issue History

Date Modified Username Field Change
2024-01-03 17:08 elong New Issue
2024-01-03 17:08 elong Status new => assigned
2024-01-03 17:08 elong Assigned To => elong
2024-01-03 17:08 elong Tag Attached: extract
2024-01-03 17:11 elong Status assigned => resolved
2024-01-03 17:11 elong Resolution open => fixed
2024-01-03 17:11 elong Fixed in Version => 3.14.12
2024-01-03 17:12 elong Issue cloned: 0006174
2024-01-03 17:12 elong Relationship added related to 0006174
2024-01-09 16:18 admin Changeset attached => SymmetricDS 3.14 f7e44073
2024-01-09 16:18 admin Changeset attached => SymmetricDS 3.15 f70233d4
2024-02-05 18:57 admin Status resolved => closed