Eric Long

Yes, use the extension ID from sym_extension as the router_type in sym_router.

It compiles your Java code on the fly and extends AbstractDataRouter, which doesn't have an "engine" member variable. It's still possible to get the engine based on the current source node ID that is running routing. Here is some example code: org.jumpmind.symmetric.ISymmetricEngine engine = null; for (org.jumpmind.symmetric.ISymmetricEngine e : org.jumpmind.symmetric.AbstractSymmetricEngine.findEngines()) { if (e.getNodeId().equals(context.getSourceNodeId())) { engine = e; break; } } I added the...

Thanks for reporting this Davide. It will be fixed in 3.16.3. https://issues.symmetricds.org/view.php?id=6910

Maybe you could add the SQL statements to set the "triggers_disabled" variable needed to tell the triggers not to capture the change: https://support.jumpmind.com/kb/article/23-Disabling-Sync-Triggers-for-Session There is also a variable called "node_disabled" that you set with your node ID. It gets recorded on sym_node in source_node_id column, which is how routing knows not to send it back to where it came from. You only need to worry about this variable if you have the sync_on_incoming=1 on s...

REST API has operations for syncing changes. But REST is not considered core to data replication and it was moved to Pro version only starting with 3.15. It's still available in older versions though.

SymmetricDS finalist for DevOps Dozen 2024

3.15.9 Released

3.15.8 Released