Set Provenance Granularity Manually
Data Hub provides three levels of granularity for provenance information: coarse (default), fine, and off.
Provenance tracking only applies to mapping, mastering, custom-mapping, and custom-mastering steps.
"provenanceGranularityLevel" : "coarse" |
"provenanceGranularityLevel" : "fine" |
"provenanceGranularityLevel" : "off" |
|---|---|---|
| Document-level provenance information is always provided by default. | Both document-level and property-level provenance information are provided. | Provenance information for the current flow or step is not stored. However, previously collected provenance information is retained; database administrator permissions are required to delete existing provenance information.
CAUTION: Do not turn off provenance unless you are certain the project will never make use of provenance information.
|
| The set of document-level provenance information to track is not customizable. | The set of property-level provenance information to track can be customized for custom steps only. A default non-customizable set is used for mapping and mastering steps. | |
| In a mastering step, the merged document includes provenance information from all its source records, in addition to provenance information about the mastering step run. |
In a mapping step, provenance information includes a field's XPath in its original document and its associated property in the entity model instance. In a mastering step, provenance information includes paths to the original records that provided the resulting value(s) of a property in the merged document. |
In a mastering step, the merged document includes provenance information from all its source records, but not provenance information about the mastering step run. |
Note: All provenance documents are stored in the
data-hub-JOBS database and are added to the protected collection http://marklogic.com/provenance-services/record.