Manta Flow Revision Difference

The Manta Flow revision difference feature makes it possible to compare two different revisions. The differences are reported in a single CSV file.

Prerequisites

Authorization is required to use this feature. The user must have the roles ROLE_USER and ROLE_EXPORTER.

Usage

To use this feature, enter an HTTP GET request by using the following format.

http://<server_name>:<port>/manta-dataflow-server/api/diff?oldRevision=<oldRevision>&newRevision=<newRevision>

where the <server_name> and <port> are provided by your application administrator.

The URL parameters:

Parameter	Description	Default value	Sample value
`<newRevision>`	The newer of the two revisions being compared	last committed revision	4
`<oldRevision>`	The older of the two revisions being compared	`<newRevision> - 1`	2

For minor revisions the following format is used (note the decreasing numbers of 0s):

Revision 2.3 = 2.000003
Revision 2.32 = 2.000032
Revision 2.340 = 2.00034

The HTTP response is of the application/octet-stream MIME type and contains the compressed difference report in CSV format.

Restrictions

The last committed revision must be at least 1 (otherwise, there is nothing to compare).
If both revisions are set, <newRevision> must be greater than <oldRevision>.
If <newRevision> is set, it must be between 1 inclusive and the last committed revision inclusive.
If <oldRevision> is set, it must be between 0 inclusive and the last committed revision exclusive.

Examples

Use case	HTTP GET request
Compare revisions 2 and 4	`http://<server_name>:<port>/manta-dataflow-server/api/diff?oldRevision=2&newRevision=4`
Compare revisions 3 and 4	`http://<server_name>:<port>/manta-dataflow-server/api/diff?oldRevision=3&newRevision=4` or `http://<server_name>:<port>/manta-dataflow-server/api/diff?newRevision=4`
Compare revision 2 and the last one committed	`http://<server_name>:<port>/manta-dataflow-server/api/diff?oldRevision=2`
Compare the last two revisions committed	`http://<server_name>:<port>/manta-dataflow-server/api/diff`

Usage with Process Manager

This feature is also available as a scenario in Process Manager. It is possible to compare only the last two versions. To do this, create a new workflow with MANTA / GENERAL / Revision Difference Scenario. This scenario is available only in the Advanced mode.

Difference Report Format

The revision difference report is stored in a CSV file. The first line is a header; the following lines represent the corresponding differences. A difference record has the following structure.

Field group	Field	Description
Object changed between the compared revisions	Object resource	Resource of the changed object
	Object name	Qualified name of the changed object
	Object type	Type of the changed object
	Object status	The object change status; possible values: ADDED—the object exists in the newer revision, not in the older one REMOVED—the object exists in the older revision, not in the newer one CHANGED—the object exists in both revisions, but its attributes are different or there is a difference in the connected objects
Connected object changed between the compared revisions This part of the record is empty if no connected object changed	Connected object resource	Resource of the connected object
	Connected object name	Qualified name of the connected object
	Connected object type	Type of the connected object
	Connected object status	The connected object status; possible values: SOURCE_ADDED—the object is connected as a source in the newer version, not in the older one SOURCE_REMOVED—the object is connected as a source in the older version, not in the newer one TARGET_ADDED—the object is connected as a target in the newer version, not in the older one TARGET_REMOVED—the object is connected as a target in the older version, not in the newer one

Example of a Report

diff.csv

"Object resource","Object name","Object type","Object status","Connected object resource","Connected object name","Connected object type","Connected object status"
"MSSQL","WIN-RRR5IO49B55/manta/dwh/SEGMENT_H","Table","ADDED","","","",""
"MSSQL","WIN-RRR5IO49B55/manta/dwh/SEGMENT_H/SEG_KEY","Column","ADDED","","","",""
"MSSQL","WIN-RRR5IO49B55/manta/dwh/SEGMENT_H/VALID_TO","Column","ADDED","","","",""
"MSSQL","WIN-RRR5IO49B55/manta/dwh/SEGMENT_H/VALID_FROM","Column","ADDED","","","",""
"MSSQL","WIN-RRR5IO49B55/manta/dwh/SEGMENT_H/PARTY_KEY","Column","ADDED","","","",""
"MSSQL","WIN-RRR5IO49B55/manta/dwh/HIST_PARTY","Procedure","ADDED","MSSQL","WIN-RRR5IO49B55/manta/dwh/PARTY_H/BIRTH_DATE","Column","SOURCE ADDED"
"MSSQL","WIN-RRR5IO49B55/manta/dwh/HIST_PARTY","Procedure","ADDED","MSSQL","WIN-RRR5IO49B55/manta/dwh/PARTY_H/GENDER_KEY","Column","SOURCE REMOVED"
"MSSQL","WIN-RRR5IO49B55/manta/dwh/HIST_PARTY","Procedure","ADDED","MSSQL","WIN-RRR5IO49B55/manta/dwh/PARTY_H/GENDER_KEY","Column","TARGET ADDED"
"MSSQL","WIN-RRR5IO49B55/manta/dwh/HIST_PARTY","Procedure","ADDED","MSSQL","WIN-RRR5IO49B55/manta/dwh/PARTY_H/ICO","Column","TARGET ADDED"
"Oracle","ORCL/DWH/REP_CLIENT/ADDRESS_LINE2","Column","REMOVED","","","",""
"Oracle","ORCL/DWH/REP_CLIENT/ADDRESS_LINE3","Column","REMOVED","","","",""

The report says:

A SEGMENT_H table with SEG_KEY, VALID_TO, VALID_FROM, and PARTY_KEY columns was added to a dwh schema (in a manta MS SQL database on the WIN-RRR5IO49B55 server).
The BIRTH_DATE column of the dwh.PARTY_H table became a source of the HIST_PARTY procedure.
The GENDER_KEY column of the dwh.PARTY_H table stopped being a source of the HIST_PARTY procedure and became a target of the same procedure.
The ICO column of the dwh.PARTY_H table stopped being a target of the HIST_PARTY procedure.
The ADDRESS_LINE2 and ADDRESS_LINE3 columns were removed from the REP_CLIENT table or view in the DWH schema (in an ORCL Oracle database).