Description
Following OAK-7510 changes there seem to be some scenarios where changes to rep:nsdata node trigger repository initialization issues.
So far I had issues reproducing but they seem to be in the area of upgrade and store composite.
I would like to reduce the strictness of the NamespaceEditor and instead of throwing an error it would rebuild its internal index node. The impact on performance would be tiny and becuase the node is rebuilt on each change there is no loss of integrity.
Will be hiding this behind a flag so various scenarios can be tested, until this issue is clarified.
Attachments
Issue Links
- relates to
-
OAK-7510 Run repository initializers with hooks
-
- Closed
-