Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.maia.ai/llms.txt

Use this file to discover all available pages before exploring further.

From time to time, to provide access to new features, Matillion will issue an updated version of software. New versions may also include bug fixes and security hotfixes. The Matillion-hosted Full SaaS will always use the latest available version. If you deploy a Hybrid SaaS in your own infrastructure, however, you have control over how and when you update the .
Matillion will not be able to guarantee support for older versions, therefore we recommend that you always run the most recent version which has been released on your version track. Version tracks are discussed below. Read Software updates and patch management for details of our support policy.

​
Version tracks

The update cadence depends on whether you chose the Current or Stable version track when you created the . Read version tracks for a full discussion of version tracks. If you have auto update enabled, your will be automatically updated to the latest version on your chosen version track as soon as it’s available. Without this option enabled, you will have to manually update to the new version. Critical security patches are only applied to the supported releases on both tracks.

​
Release cadence

releases are made on the following cadence:
  • Current track: Usually twice a week, typically on a Tuesday and Thursday, though this may vary. These releases may include new features, bug fixes, and security patches.
  • Stable track: Once per month, on the 1st of the month.
  • The Matillion for Snowflake is updated once per month on the second Tuesday of the month.
If you need to change the track that an existing is on, you can use the Update a public API endpoint. However, take note of the following:
  • Changing the ‘s version track does not update the itself. You must update the image URI for the service in your cloud provider. If you don’t, the version may show as “Out of support”.
  • If you change the state from Current to Stable and update the installed service, pipelines created using a newer (Current) version might not run as expected on an older (Stable) version.

​
Auto update

By default, s are created to automatically update. However, you can opt out of this process.
If you opt out of automatic updates, ensure you have a manual update procedure in place. Read our support policy. If you are using the Current track and wish to opt out then it may be prudent to use the Stable track instead due to the faster update cadence of the Current track.
The standard installation uses a tagged container image on the container repository. This tag is always kept on the most recent released image for a given version track. If the installation in your cloud infrastructure is set to always pull the latest version, then whenever a instance is started, it will always pull this latest version. This means that whenever you restart a , it will be automatically updated to the latest release on its version track, regardless of whether auto update is enabled or not. If your has multiple instances, and one instance happens to be on a later version than another due to the timing of restarts, then the reported version of the will always be the lowest version of any instance, and the availability of features will be linked to that lowest version. If a has auto update enabled, then whenever a new version is released on its version track (Current or Stable), the will be automatically updated to that version. You can change a ‘s auto update status at any time from the details screen. The auto update process will issue a graceful shutdown command to the when a new version becomes available. This allows the to finish the task it’s working on before shutting itself down. The will then restart, and as part of the restart process will automatically update to the latest available version of the . If auto update is not enabled, you will be notified when a new version is released, and must manually update the . If a falls behind the latest release on the version track because you have disabled auto update, and you then enable auto update, it will not immediately update itself to the latest available version. The update will only be triggered when the next version is released on its version track, or if the is restarted for any reason, in which case it will always update to the latest available version.

​
Snowflake

For update information about Hybrid SaaS s installed in Snowflake using the Native App, read Updating s section.

​
Manual update

If you haven’t enabled auto update, you will need to check whether a new version is available on your version track. In the list of s, the text Update Available is displayed below the version number if a new version is available. Additionally, the latest available version number, version release date, and an update notification will be shown on the details screen. To update the manually, follow the process given in Restart a . Restarting the automatically updates it to the latest release on its version track, as long as the installed is always pulling the latest image. If your service isn’t configured to pull a new image on restart, you should use the pause command to put your into a safe state where it can be restarted manually from your cloud provider. You can also update the from the runners API endpoint. The endpoint can also be used to determine whether a new version is available. For further details on using the API, read API overview.