Managing versions
The Data Integration versioning lets you create multiple versions of a Data Flow saved in a timeline view. Each version captures the Data Flow state at a particular time. This helps to track and revert to specific versions as needed.
Timeline view
The timeline view in the Data Integration versioning system shows a list of all versions of a Data Flow, sorted by the date and time. You can quickly access any version by clicking on it.
Each version includes the following details:
- Version Name - defaults to the version creation date if not set.
- Version Status - shows the latest Version.
- Version Create Date - shows the version created date.
- Versions Created By Name - shows the user's name who created the version.
Clicking on a version from the list shows the definition of the saved version on the Data Flow. This is a read-only mode, so no changes are allowed. Select the Display only bookmarked versions option to view all bookmarked versions.
Version types and limits
Two types of Versions:
-
Un-bookmarked versions - The system automatically saves the default versions. You can have up to 70 Un-bookmarked versions. When a Data Flow has reached its version limit, the system replaces saved versions with the latest one.
You can have up to 70 Un-bookmarked versions.
-
Bookmarked versions—The distinct versions you want to use remain preserved when the maximum number of versions is reached.
You can have up to 30 bookmarked versions.
Bookmarking a version
- Navigate to the Data Integration Console.
- Click the star icon next to the Data Flow version.
- If you have reached the bookmark versions limit, you can do one of the following:
- Let the system delete the oldest bookmarked version to save the current one.
- Manually remove a bookmark by clicking the star on another version.
- You can view a bookmarked version with a full star.
Editing a version
- Click the star on another version.
- Click the Edit button and enter the version name.
- Click Save.
Restoring a version
- Click on the desired version of a Data Flow.
- Click Restore to this version to view and restore this version.
This replaces the current version of the Data Flow with the selected version.
If the version limit is reached, the system automatically deletes the earliest version to make space for the restored version.
Data Flow configuration components excluded from versioning
The changes to the following topics in a Data Flow do not trigger an automatic version creation, as they are excluded from version tracking.
-
Date range - changed manually or through a scheduled run.
-
Data Flow group
-
Data Flow schedule
-
Notifications.