I think you were heading down the right path with a bsh router. You could do something like the following in a bsh router.
targetNodes.add(dataMetaData.getTable().getNameLowerCase().substring(6));
return targetNodes;
targetNodes.add(dataMetaData.getTable().getNameLowerCase().substring(6));
return targetNodes;
I was setting up the other direction
I believe you can refer to parameters in the target table name on a router though
I see, you mean I set up my value in 'target_table_name' directly in sql with sys_log$(node_id)
so routing would run at each store and the node id is a built in parameter
I believe it is $(variable name)
Could not find the target table 'platform-ops.syslog$(node_id)'
$(sourceNodeId)
still not working :(
yes @joshahicks I tried with target catalog, it can be resolved but not for table
thank you help help
thanks for your help
@joshahicks
The version is 3.10.4
Hi~How does symmetricds implement file synchronization, is there a sample configuration file? Thank you!
@yaoshenshen yes you can send create events on demand for each table. If the target table does not match the source it will automatically alter. Here is an example of creating a create event
dataService.insertCreateEvent(targetNode, triggerHistory, triggerRouter
.getRouter().getRouterId(), false, -1, createBy);
@guozhishan File sync is a bit complicated to explain over chat but check sections 4.7 and 4.8 in the guide.
http://www.symmetricds.org/doc/3.10/html/user-guide.html#_file_triggers
@yaoshenshen if your using MSSQL server there is a parameter to capture DDL changes and autmatically sync. trigger.capture.ddl.changes
@nuoyaneasy unfortunately we confirmed in our lab yesterday that the variables only apply to target catalog and target schema currently on the routers. It should be a simple addition to apply to tables as well. Created an issue.
https://www.symmetricds.org/issues/view.php?id=4158
https://www.symmetricds.org/issues/view.php?id=4158
"Data cannot be retained in table" ... "because of the addition of the required column" <- why is that the case? Why does adding a column make symmetric orphan existing data into a table with _ at the end and start over with a blank table? is there a place to control this behavior? even having a reload-table fire would be more desirable than a blank table.
It is because you are adding a new column that is required but does not have a default value. As a result it can not add the rows back to the table without putting fake data in here so it retains it in a temp table. If you add your new required column with a default value this would work.
I see. In my case, these schema changes are controlled by the application (microsoft dynamics nav) so I can't change that behavior (of new columns having no default value). Is there any configs or controls for having something like a table-reload initiated when schema changes lead to data not being retainable?