I think you are looking for $(groupId) https://github.com/JumpMind/symmetric-ds/blob/f590c705d145519763dfe97146430c69368fc5e0/symmetric-core/src/main/java/org/jumpmind/symmetric/db/AbstractTriggerTemplate.java#L239-L247 Documentation mentions it here: http://www.symmetricds.org/doc/3.9/html/user-guide.html#_load_data Variables are discussed here: http://www.symmetricds.org/doc/3.9/html/user-guide.html#_variables We are always looking to improve the documentation. Please feel free to create pull requests...
What database are you using? SymmetricDS has good bulk loaders for a few different databases. You also get some concurrency by creating multiple reload channels and putting them on different channel queues.
I would look at sym_data on node 2 to track down what happened. It should have a record of all the changes and where they came from.
The error_flag indicates that there was an error that occurred. It remains set until the status changes to OK. You see the LD status for multiple batches because they are sent according to max_batch_to_send. Acks don't come back until all batches in one sync are processed. Depending on your sync scenario you could set max_batch_to_send to 1 to get a more real time status update. You would want to set the push and pull jobs to run much more often if you do. If you monitor for the error_flag on either...
We tried this with your query and had no issues. Any other details that you can provide us would be great.
Did you set create.table.without.defaults=true at the source before the initial load was created?
If you can get us enough information so that we can recreate the issue we'll fix it. Can we get your configuration, engine.properties settings, a dump of outgoing_batch where load_id={failed load id} and the count of the number of rows in the failed table and the symetricds log file?
If newer versions file.sync.enabled is defaulted to false. Is this your issue?