View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003871 | SymmetricDS | Improvement | public | 2019-02-04 16:26 | 2019-04-25 20:17 |
| Reporter | pmarzullo | Assigned To | |||
| Priority | normal | ||||
| Status | new | Resolution | open | ||
| Product Version | 3.9.17 | ||||
| Summary | 0003871: Changing target catalog/schema on router does not affect outstanding batches | ||||
| Description | User had a batch in error because the table that didn't exist in the default catalog/schema. Then, user updated the router to specify the correct catalog/schema. And they also added new tables to the router to see those batches load successfully. But the original batch stayed in error, because it was already extracted into staging. Is there a way to detect a target catalog/schema configuration change and clear staging for those batches? Maybe query for batches that contain the same router_id? Alternatively, is there a way to make it more clear to the user how the system works, so they ignore the batch or cancel the load while testing configuration? | ||||
| Tags | extract | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-02-04 16:26 | pmarzullo | New Issue | |
| 2019-04-25 20:17 | elong | Summary | Create ability to stop/start different functionalities of channel synchronization => Changing target catalog/schema on router does not affect outstanding batches |
| 2019-04-25 20:17 | elong | Description Updated | View Revisions |
| 2019-04-25 20:17 | elong | Tag Attached: extract |