[OPENDJ-6431] Support replication of offline updates to LDIF backends Created: 04/Jul/19 Updated: 07/Jan/20 Resolved: 16/Jul/19
|Reporter:||Matthew Swift||Assignee:||Michal Severin [X] (Inactive)|
|Epic Link:||Replication self-registration|
DJ has always attempted to support replication of offline changes to the schema backend. However, this support is not available for LDIF backends and, in particular, cn=admin data where symmetric keys are located.
Steps to reproduce:
This bug is particularly important from a devops / automation point of view where servers may import data during a bootstrap phase.
|Comment by Matthew Swift [ 09/Jul/19 ]|
Fix has been merged, although the unit test coverage is not very good because a significant amount of refactoring is required. In particular, it would be nice to check that the LDIF backend detects offline changes as follows:
Unfortunately, the existing unit test depends on the server running. To close the backend we need to stop the server, make changes and then restart. However, the server restart will automatically flush out the offline changes. A better approach would be to refactor the LDIF backend tests so that they are true unit tests that do not depend on the server running and, instead, use mocked config and server context.
|Comment by Michal Severin [X] (Inactive) [ 07/Jan/20 ]|
Verified with 7.0.0-SNAPSHOT rev. 1d33bc905c3