<@U0A71G31CDV> There exist `4.1.1` tag and docker ...
# questions-and-troubleshooting
u
@Rocky There exist
4.1.1
tag and docker image, but there's no release note on github Release list. Cloud you explain why?
r
StarRocks v4.1.1 was indeed released on May 29, 2026, but you may not see it on the primary GitHub Release list because it was fast-tracked as an urgent patch specifically for container environments. The main reason for this version's release—and why it appeared on Docker Hub immediately—was to fix a critical unstable load order issue in the v4.1.0 container image (tracked in issue #71825). This bug caused Backend (BE) processes to fail to start reliably in Docker/Kubernetes environments, making v4.1.0 unusable for many container users. Where to find the Release Notes While the GitHub Releases page sometimes lags behind for rapid patch releases, full release notes are published in the official StarRocks documentation: * StarRocks v4.1 Release Notes Key Changes in v4.1.1 Beyond the Docker fix, v4.1.1 includes several notable updates: * Behavior Changes: * The Hive connector now uses a native C++ Avro scanner by default (replacing the JNI version). * Query rewrite is now disabled for INCREMENTAL/AUTO materialized views to prevent incorrect results in unsupported rewrite scenarios. * Improvements: * Java UDFs now support
STRUCT
arguments, nested `ARRAY`/`MAP` types, and
DECIMAL
types. * UDAFs are now loaded/initialized once per query and reused, reducing overhead for high-concurrency pipelines. * Iceberg: Completed support for
timestamptz
partition transforms on the sink side. If you are using Docker or Kubernetes, it is highly recommended to use 4.1.1 instead of 4.1.0 to avoid the startup issues.