Description | The auto.reload.reverse feature is a wonderful addition to the feature set, but it doesn't respect the datareload.batch.insert.transactional parameter and always inserts the reload events on separate transactions. This causes havoc on a system in which the data is changing for obvious reasons. I have created a patch for 2.5 that will add support for a transactional reverse reload and have attached it to this issue. I thought a bit about whether the other initial load parameters such as initial.load.delete.first, initial.load.create.first, or initial.load.delete.first.sql should be supported on a reverse initial load and I guess to me they seem more appropriate for a registration server than a registering node. Please feel free to provide feedback if there is you would like anything different in this fix, I would be happy to refactor it or add to it. |
---|