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 has been archived by the owner on Nov 9, 2022. It is now read-only.
Currently when a merge happens it adds all the properties to the audit file, even if the new source file and the mastered document are the same. The desire would be to have a section which only store the changes that happened. Right now its very hard to tell what changed with out going through each of the properties in the audit document.
IE: If we have a member document and the only thing that changed was the First name, then all the elements in that documents would be stored in the audit file with the master value as well. The new changed section would only store the first name values.
This becomes a big problem when loading a batch file of 1,000s of new documents that are mastered and then you want to see what changes happened for that batch. The batch is stored in the header, so you know what documents to look at. But right now you'd have to pull out each document and compare each property of the document to see the changes. This is very expensive to do at query time. Since SM already has to look at each property it would be idea to push the cost to there.
The text was updated successfully, but these errors were encountered:
freshie
changed the title
Ability to configure audit document to not keep exact matches
Keep a section in the audit file that has just the changes
Dec 6, 2018
Currently when a merge happens it adds all the properties to the audit file, even if the new source file and the mastered document are the same. The desire would be to have a section which only store the changes that happened. Right now its very hard to tell what changed with out going through each of the properties in the audit document.
IE: If we have a member document and the only thing that changed was the First name, then all the elements in that documents would be stored in the audit file with the master value as well. The new changed section would only store the first name values.
This becomes a big problem when loading a batch file of 1,000s of new documents that are mastered and then you want to see what changes happened for that batch. The batch is stored in the header, so you know what documents to look at. But right now you'd have to pull out each document and compare each property of the document to see the changes. This is very expensive to do at query time. Since SM already has to look at each property it would be idea to push the cost to there.
The text was updated successfully, but these errors were encountered: