Migrating to Starburst Enterprise 433-e or higher#

Starburst Enterprise platform (SEP) 433-e uses Starburst Ranger which includes changes to RBAC policies that may require migration. If you use Apache Ranger as a role-based access control system alongside SEP, follow this guide to migrate to 433-e and higher.


The Starburst Ranger CLI tool now includes the migrate command, which is used to upgrade the Starburst service definition in Ranger and migrate existing policies automatically.

Starburst Ranger contains a script that is executed on Docker container start, by default. The script automatically updates the Ranger service definition for the Starburst service, which links the SEP version and Starburst Ranger version.

The following migration guide details the required actions for migrating Ranger to SEP 433-e. Contact Starburst Support with questions or feedback.

Before beginning the migration process using Starburst Ranger, it is highly recommended to do the following steps:

  • Backup the Ranger database. Doing so allows you to restore any lost Ranger policies, if an unexpected error occurs while the migration command is running.

  • Update the SEP cluster to 433-e before upgrading Starburst Ranger to version 2.3.0-e.11 or higher. Using Starburst Ranger version 2.3.0-e.11 or higher with a SEP version lower than 433-e might automatically update the Ranger service definition, which makes the new version of Starburst Ranger incompatible.

Complete Ranger migration#

To migrate the Ranger database, follow these steps:

Step 1: Make sure the Starburst Ranger CLI is installed

Install the CLI, if it is not installed.

Step 2: Run the migrate command

Run the following command to connect to your Ranger database and perform the automated migration:

starburst-ranger-cli migrate –properties=ranger-access-control.properties

If the connection fails, ensure that the ranger-access-control.properties exists and includes complete and accurate connection information.

Step 3: Ensure a successful migration

After the command executes, the end of the output should be a JSON value with information pertaining to the execution of the command, the success of the execution, and any errors:

  “executed”: 1,
  “success”: true,
  “errors”: []

Any entries in the error field indicate an unsuccessful execution. Refer to the following steps to troubleshoot:

  • Analyze the error to determine the appropriate steps to take to resolve the error.

  • In Starburst Ranger services, check the number of Ranger policies before and after the migration to determine if any policies were lost.

  • If any Ranger policies were lost, revert to the Ranger backup, and retry the migration.

  • If the error persists, contact Starburst Support.