Selecting and Changing Hybrik Versions

Hybrik regularly releases new software versions. When you create a new computing group, you choose which version of Hybrik that your computing group will run. For more on creating a computing group, refer to our guide to setting up a Computing Group.

To get a quick view of the Product Version that your computing group is running, you can navigate to the Machines > Configuration page. If it doesn’t appear as a column in the list, choose the gear icon:

And select Product Version:

Always Use Latest vs “Locking” a version

Under the Machines > Configuration page of the Hybrik Web Console, you can see all of your computing groups. Choose “Edit” or “New Computing Group” to select a product version.

When you create a new computing group, you must select an option for which Product Version to use. The first option is Always use latest, currently: [version], [release_date]. Below that option, there are specific versions listed.

Always Use Latest

Always Use Latest will automatically upgrade your computing group to the latest version whenever Hybrik releases a new product version. This ensures that you get the latest and greatest features and bug fixes. If, however, you have a production workflow where you have verified a job’s outputs and want to ensure no chance of changes, you will want to “Lock” to a specific product version of Hybrik.

Locking to a Specific Version

Select any product version that is listed below Always use latest. Once selected, this computing group will always use this version of Hybrik, even if a new version is released.

Multiple Computing Groups

Remember that Hybrik versions are set per computing group. If you wish to upgrade one or more groups, you will need to upgrade each one by clicking on the computing group and choosing “Edit” from the menu.

Upgrading

When you upgrade a computing group, any machines that are running will terminate when they have finished their tasks. New machines will be launched with the newly selected product version to service new tasks. Depending on the runtime of any currently running tasks, it may take several hours for all machines running the previous version to shut down.

Testing a new product version

When Hybrik releases a new product version, you should re-test your workflows to ensure there are no unintended effects to your outputs. For an example of how to do this:

1. Create a new computing group, select “Always Use Latest” for a Product Version
2. Add a mandatory tag of TESTING and press “Save”
3. In your job, you can use the task_tags of TESTING for your job - all tasks in this job will use this new “testing” computing group to run the job using the latest product version. task_tags is a shortcut for setting task.tags for each task in your job. You place it at the root level of your job.

{
    "name": "Tagging Example",
    "task_tags": [
        "TESTING"
    ],
    "payload": {
        "elements": [
            {
                "uid": "source_file",
                "kind": "source",
                ...
            

For more on how to use tags, see our Tagging Tutorial.

Testing Order

1. We recommend testing first in your development environment such as demo.hybrik.com.
2. Once you have validated your Hybrik version and computing groups and checked your output, we recommend running a manual test in your production environment. This serves as a sanity check to make sure that any updated configurations in your production environment mirror your test environment. This will usually catch things like missing licenses, computing group tags, or other discreprencies between environments.
3. Lastly, once you performed a sanity check in your production environment, you can proceed with fully upgrading the workflow.