View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004077 | SymmetricDS Pro | Bug | public | 2019-08-23 12:15 | 2024-06-17 17:58 |
| Reporter | hanes | Assigned To | |||
| Priority | normal | ||||
| Status | confirmed | Resolution | open | ||
| Product Version | 3.10.3 | ||||
| Summary | 0004077: Load Data w Wildcards functions incorrectly if you choose "Select Tables" and select just one table with one-to-many sync | ||||
| Description | Corp to Store, with a trigger of wildcard case of item* which matches three tables. Go to the Load Data Screen. Choose all destination nodes (in my case, two) Go with "select tables" and then pick just one of the tables from the list of tables that resulted from the wildcard. The outgoing batches get generated, but... a) there's just one load_id created (there should have been two), and b) the load id itself doesn't show up as a row in the Load Data screen's list of loads Expected behavior was a separate load id for each node, and for the two loads to show on the Load Data screen. | ||||
| Tags | No tags attached. | ||||
|
|
FYI, the load doesn't show in table sym_table_reload_request either. |
|
|
The screen displays based on trigger router table normally, which translates perfectly into a reload request. When using a wildcard one trigger router equals multiple tables, it cannot use trigger router instead it uses trigger history. Cannot create a load request with a single trigger history. So instead it puts a reload event into sym_data. Routing assigns load ids to any reload event that it comes across. |