0003871: Changing target catalog/schema on router does not affect outstanding batches - SymmetricDS

Summary	0003871: Changing target catalog/schema on router does not affect outstanding batches

Revision	2019-04-25 20:17 by elong
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?

Revision	2019-02-04 16:26 by pmarzullo
Description	Synchronization Routing Data Extraction Data Loading This will allow configuration to be changed without messing up any of those areas. For example, when changing out a router (replacing an existing router with a new one), any unsynchronized outgoing batches are associated with the old router, then when the configuration replaces the old router with the new router, the synchronization of those existing batches will fail.