Starburst developer blog

The latest news from our users, engineers, writers, and product folks for all our peers and friends out there.

Want even more updates and information? Go to the Starburst company blog.

Starburst Enterprise 367-e STS

Promise! This is the last Starburst Enterprise platform (SEP) release of the year 2021.

With our recent LTS backport release train in your hands, we just had to cut a release of a new STS to finish up the work around log4shell.

Of course the release includes more than just upgrades and removal of unused log4j binaries. In fact, if you look at the 367-e release notes and the 365-e release notes you see a number of new features and changes that are definitely worth trying out. Specifically our new default web interface for SEP includes numerous things to play with:

Even if you are still running the 364-e LTS release in productions, I strongly suggest you play with the new 367-e release. And of SEP even more for the next releases. There is plenty coming in 2022.

Manfred and Matt

Update, 2022-01-27:

In 368-e and 367-e, writing to Hive, Iceberg, or Delta tables on S3 or S3-compatible storage with a streaming upload enabled can write corrupted data files without reporting an error back to the users.

In 368-e streaming uploads are enabled by default. As a results users may encounter this without taking any action to enable streaming in their configuration.

In 367-e streaming upload are disabled by default. However it is a common practice to enable streaming.

As a fix we recommend to set hive.s3.streaming.enabled=false and trino.s3.streaming.enabled=false in all catalog property files using S3 with the Hive, Iceberg or Delta Lake connector.