You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 9, 2022. It is now read-only.
As a developer I want the ability to configuration with in my match options to turn on and off re-mastering.
re-mastering happens when a document has already been master and is in the archive but the uri is sent to process through something like the rest endpoint. This becomes and issue when you have already match the document and its been being sent to master.
It happens easily if you have some out side of marklogic orchestrating mastering. Such as Nifi. If Nifi gets a list of uris that are ready to be mastered and sends them in batches or 1 by 1 it doesn't know whats already been matched. So it will just send the list of uris and some of them will be already matched from the a uri that went before that was a match to it.
example:
document a matches document b and c.
Document A gets processed first. and matches with document b and c.
Document B gets processed and is in the archive but our match options dont care, so document A and C get mastered in B and now their are more than one document that has the active mastered collection because both document A and B were assigned in in their own process.