Warning - Version 1.74 & S3 issues

Hi Everyone,

 

I just wanted to share that the fixes have been released as per 1.74.5, our release notes are being updated as I share this but I wanted to let you know at the first opportunity as promised, they can be found here.

Customers on the 1.74 STS are able to make an in-place upgrade to get these fixes.

 

Kind regards, Joe

That's great, thanks @JoeCommunityManager​ for the regular updates. When the new release it out, it would be great to get some information around exactly what fixes have been applied (i.e. exactly which issues your Engineers have addressed) so that we can verify that they correspond to the problems we'd encountered.

Hi @Michael

I hope you are well, I am sorry to hear you have encountered this after upgrading, I would strongly recommend raising this with our support team, they can look into this issue in more detail and get to the bottom of that.

if you would like any help just let me know.

Kind regards, Joe.

Hi @emoncada

I am sorry to hear this, but thank you for raising it with us, I am going to raise this internally and let the team know, similar to Michael, this will need a closer look and the support team will be able to do this, please raise a case and they can look into that for you.

If you need anything else, please let me know.

Kind regards, Joe

Thats a possible solution - however, you'll lose the ability to browse around in the buckets. And more important, you have to include the credentials in the custom SQL :( We're only using the SQL for json unloads as this is currently not supported out of the box and the creds are coming via a global variable. However, not that fancy solution/workaround...

We quickly tested 1.74.4 as well - good news: They fixed the s3 load (browsing even faster then before). However, they missed all the other components :( For example, data transfer is still broken when the source s3 is selected.

Word for word, this was our support agent's response:

 

"At the moment, version 1.74 is full of issues and we are starting to recommend everyone stays away from 1.74"

 

So to answer your question, I highly doubt the two issues bulleted in the release notes are the extent of the problems. "Full of issues" seems like it would definitely be more than just two, and I honestly don't think I've ever heard a support rep say anything less re-assuring than that in my career.

Hi @ewa.lipinska

Thanks for asking that, there will be in the documentation here, once said fixes are released, I will also share a breakdown here for further visibility.

Kind regards, Joe

Hi @JoeCommunityManager​ ,

Should this work for 1.74.4 as well? As of now, I dont see a newer version:

Current Version: 1.74.4

$ Last metadata expiration check: 21:35:02 ago on Tue Mar 19 09:14:26 2024.

$ Available Packages

$ matillion-universal.noarch 1.73.1-1 MatillionUniversalRPM-Stable

$ matillion-universal.noarch 1.74.1-1 MatillionUniversalRPM-Stable

$ matillion-universal.noarch 1.74.2-1 MatillionUniversalRPM-Stable

$ matillion-universal.noarch 1.74.3-1 MatillionUniversalRPM-Stable

$ matillion-universal.noarch 1.74.4-1 MatillionUniversalRPM-Stable

$ Last metadata expiration check: 17:49:01 ago on Tue Mar 19 13:00:26 2024.

$ Available Packages

$ matillion-universal.noarch 1.72.4-1 MatillionUniversalRPM-LTS

$ matillion-universal.noarch 1.72.5-1 MatillionUniversalRPM-LTS

$ matillion-universal.noarch 1.72.6-1 MatillionUniversalRPM-LTS

$ matillion-universal.noarch 1.72.7-1 MatillionUniversalRPM-LTS

There are no upgradable versions available.

Just to add as promised @ewa.lipinska

A breakdown of what has been fixed in this release:

Bug fixes

  • Fixed an issue where spaces in Amazon S3 bucket and folder names were not being treated as valid.
  • Fixed an issue where folders in an Amazon S3 bucket were being listed as files in the file selection dialog for certain components.
  • Fixed an issue that was causing the thread count to increase until the Matillion ETL instance stops responding in some circumstances.
  • Fixed an issue that caused the S3 Load component to be unable to access S3 buckets in a region different from the one the Matillion ETL instance is hosted in.

I hope this helps and has fixed any issues you had encountered.

Kind regards, Joe

Hi @ewa.lipinska@wes.morton

I am sorry this is the case and thank you for your feedback and for letting me know, I am now in direct conversation with the team that is working on this and will have a full in-depth response for you shortly. If you want to add anything else, please just let me know here.

Once I have more information, I will post it here at the first opportunity.

Kind regards, Joe

Thank you for this notice and confirmation.

We noticed issue with validation of components as well (raised support ticket) and bug in "Calculator" component, addressed that one as well.

Thanks @andrea.miljus

That is very helpful for the team, we appreciate you sharing that with us.

Kind regards, Joe

Thanks for sharing that @wes.morton​ -- to be fair, I'd rather Matillion be frank with us and let us know things are not fixed yet rather than prompt us to keep updating to new patches that won't necessarily work!

Hi @ewa.lipinska@wes.morton@andrea.miljus

I just wanted to get a full update for you all with regards to the S3 issues you have been experiencing, I can confirm this is a priority for our team and they are working hard on it as we speak.

A number of fixes have gone in to remedy this and are currently being tested, the process for this is quite stringent as there are many permutations of bucket setups to test against.

If this testing is successful we will be pushing a quick release of 1.74 to include them.

Please let me know if I can help in any way, I appreciate your patience and support during this.

Kind regards, Joe

@ewa.lipinska​ Agreed, I appreciate the transparency. Thanks @JoeCommunityManager

@wes.morton@ewa.lipinska​ You are welcome, its why I am here :)

If you need anything please let me know.

I will be back with the information as I get it.

Kind regards, Joe

Hi Joe,

Thank you for providing updates on this topic, very useful.

Do you maybe have information when will next Long-term support (LTS) will be available?

 

Thank you!

 

Hello @andrea.miljus

Thanks for your question, all information on releases and Long-term Support can be found in our documentation, this will be updated first with any news on this.

Kind regards, Joe

Update: The update is now here - we're currently checking but seems good so far!