Testing a new processing engine version

Space Administrators can independently choose for each space what release version of the data loading and processing functionality to use. Birst does not automatically update spaces to use a newer version of the processing engine but we recommend upgrading your spaces to take advantage of new features related to the processing engine code.

Note: Check the Release Report for information about the improvements included in a new processing engine version.

To test a new processing engine version, you can use the Process Engine Version field in Space Properties.

The Process Engine is a component of Birst that handles the data processing that occurs when source data is pulled into the Birst data store (warehouse). The Process Engine is versioned separately from the main Birst application. Normally, the Process Engine Version can be a few versions behind the main application version.

Space Administrators normally update the Process Engine Version when there are particular features that require a newer version, such as to support a certain database for the warehouse.

Note: Birst does not automatically upgrade the Process Engine Version.

Create a copy of your existing development, test, or QA space. See Copying a space.

Note: Do not use a production space.
Navigate to Space Management for the space copy, then select Space Properties.
From the General tab, set the Process Engine Version to the release engine you want. You can select: PRD, BETA, or MRC.
Optionally, you can select Allow Retry Failed Load to automatically retry a previously failed load of data on a previous version.
Load data and process tasks in this space using the new Process Engine Version.
Verify that there are no errors and that your data is correct by:
- Using the Details link on the Process Data page
- Checking data is returned on any Dashboards in the space
- Creating new reports in Designer and Visualizer