The Catalog supports versioning, which is the ability to create a new Catalog version in the neo4j Graph DB every time the Discovery process runs and finds differences when comparing with the previous version.
A user can view each version separately or check the differences between 2 selected versions using the Catalog application, as described below.
Every time the Discovery job is executed, it performs the comparison between the current results and the previous Catalog version of the same data platform. The changes can be either due to the data source changes (such as a new table or a field) or due to the configuration changes (such as a new profiling rule or an update of an existing one).
If the Discovery process doesn't identify any changes either in the data source or in the configuration rules, it doesn't create a new Catalog version.
If the changes are found, a new version is created and the can be analyzed by version comparison, as explained further in this article.
Additional trigger for a version creation is a manual edit of the Catalog.
Click here for more information about manual overrides.
By default, the Catalog application displays the latest available version. To view any version, open the version's drop-down list and click a version number:
The Catalog tree is then displayed using the standard coloring scheme, where all the nodes are blue and the relations are orange.
To compare 2 versions, click the comparison icon in the version's drop-down list. The Catalog tree is then displayed using the comparison coloring scheme, indicating the differences between the 2 versions, as follows:
To return to a regular view mode, open the version's drop-down list again and click a version number.
Show Updates Only
When a Schema contains too many Datasets, it might be difficult to identify the updated nodes. To view updated Datasets only, you should first expand the Datasets and then click the "Show updated only" icon in the Catalog's legend. Note that this icon is only visible in the version comparison mode.
The Catalog supports versioning, which is the ability to create a new Catalog version in the neo4j Graph DB every time the Discovery process runs and finds differences when comparing with the previous version.
A user can view each version separately or check the differences between 2 selected versions using the Catalog application, as described below.
Every time the Discovery job is executed, it performs the comparison between the current results and the previous Catalog version of the same data platform. The changes can be either due to the data source changes (such as a new table or a field) or due to the configuration changes (such as a new profiling rule or an update of an existing one).
If the Discovery process doesn't identify any changes either in the data source or in the configuration rules, it doesn't create a new Catalog version.
If the changes are found, a new version is created and the can be analyzed by version comparison, as explained further in this article.
Additional trigger for a version creation is a manual edit of the Catalog.
Click here for more information about manual overrides.
By default, the Catalog application displays the latest available version. To view any version, open the version's drop-down list and click a version number:
The Catalog tree is then displayed using the standard coloring scheme, where all the nodes are blue and the relations are orange.
To compare 2 versions, click the comparison icon in the version's drop-down list. The Catalog tree is then displayed using the comparison coloring scheme, indicating the differences between the 2 versions, as follows:
To return to a regular view mode, open the version's drop-down list again and click a version number.
Show Updates Only
When a Schema contains too many Datasets, it might be difficult to identify the updated nodes. To view updated Datasets only, you should first expand the Datasets and then click the "Show updated only" icon in the Catalog's legend. Note that this icon is only visible in the version comparison mode.