Contribute in GitHub: Edit online

How to Delete Revisions

This page explains how to delete the last committed revision, any previous revisions, and uncommitted revisions. This can be accomplished through Admin UI or the command line.

Deleting Revisions with Admin UI

Deleting the Last Committed Revision

Open Manta Admin UI, and then continue with the following steps.

1. Select the Process Manager tab at the top of the page.

2. Click the Execute Workflow button at the lower left.

3. Choose the tab entitled Scenarios at the top of the pop-up.

4. Select Manta.

5. Choose to run Delete Last Committed Revision Scenario.

Deleting Old Revisions

IBM Manta Data Lineage allows to automatically maintain the number of revisions to be kept in the repository by pruning the old revisions out of the repository. You can delete old revisions in ascending order using the property Number of Historical Revisions.

1. Click the Configuration tab.

2. Select CLI in the left panel.

3. Choose Common.

4. Select Common Config.

5. Change the value of Number of Historical Revisions to the desired value.

The Number of Historical Revisions will be preserved during a new scan.

Here is an example.

If the Number of Historical Revisions is originally set to 10, after changing the value to 8 and running a new scan, you will see revisions 2 through 10, and revisions 0 and 1 will be purged.

Deleting Uncommitted Revisions

1. Navigate to the Process Manager tab.

2. Select Execute Workflow at the lower left.

3. Choose Scenarios.

4. Choose Manta > Manta.

5. Find and run Rollback Revision Scenario.

Deleting Revisions Via the Command Line

Deleting the Last Committed Revision

Use Manta Orchestration API scripts to run deleteLastRevisionScenario.

Deleting Previous Revisions

Use Manta Orchestration API scripts to run pruneRevisionScenario.

Deleting Uncommitted Revisions

Problem

A Manta Flow analysis run has failed, returning code 1 with the error message "*Server is not ready to accept new data” and/or "Error during fetch committed number. There is an uncommitted revision.*"

Solution

This happens when a transaction is already open when an analysis run tries to start its transaction. You need to determine whether another analysis is/was running at the time or whether the previous analysis run was interrupted before completion.

• If another analysis is/was still running, there is no need for intervention. However, consider changing the schedule so that the previous run has enough time to finish before the next run starts.

• If the previous run was interrupted before completion, you need to manually roll back the incomplete transaction by running:

  • For Unix:
    bash <MANTA_DIR_HOME>/scenarios/manta-dataflow-cli/bin/rollbackRevisionScenario.sh

  • For Windows:
    <MANTA_DIR_HOME>\scenarios\manta-dataflow-cli\bin\rollbackRevisionScenario.bat

• If no analysis is currently running and you are not sure what caused the failure, roll back the transaction in the way mentioned in the previous option. Either the rollback will go through without errors (signifying an interrupted analysis run) or it will fail without affecting the metadata repository (if the reason was a concurrent analysis run). Either way, the metadata repository is now ready for the next analysis run.

• If none of the above helps, you can still roll back the newest uncommitted revision on the server by opening this URL: <manta-server-url>/api/revision/rollback-current-revision.