Tech note 22/06/2020

Tech note 22/06/2020


Update: 23/06/2020 - 22:00 GMT

We have solved this issue and are releasing the fix as Matillion ETL versions:

  • 1.42.14
  • 1.44.17
  • 1.46.7
Please upgrade to the version that closest matches that of your instance. For 1.46.7 this means simply following the recommended update route. For earlier versions, please see Updating to a Specific Release.

Thanks for your patience during this time and please do not hesitate to Contact Support for help during this process.





Update: 23/06/2020 - 10:00 GMT

We have determined that a change to the Redshift cluster schema is impacting users who access external S3 data via Amazon Spectrum.

At this time, we highly recommend that you do not update your Redshift cluster unless absolutely necessary.

To prevent updates to your Redshift cluster, please see AWS Cluster Management Guide and change from “Current” to “Trailing” maintenance track. If your cluster has already updated during a maintenance window, or you need to update for another reason, here is a workaround:

Replace the affected Table Input components within transform jobs with SQL components, and write the appropriate SELECT statement manually.

Although not ideal, it will help you keep your critical ETL workflows working while we quickly resolve this issue.

We are actively building and testing a fix for an urgent interim release.



Update: 22/06/2020 - 17:02 GMT

It has come to our attention that some users may experience issues using the Table input component with External Tables after recently upgrading Redshift cluster versions to 1.0.16505. This is due to a change within the Redshift update itself. To ensure Matillion ETL will work, we highly recommend not to update your Redshift cluster unless absolutely necessary.