This topic describes the versioning, version mappings, and product lifecycle policy for the E-MapReduce (EMR) Serverless StarRocks software stack.
Background information
The StarRocks open-source community continuously evolves. New StarRocks versions provide advanced features, such as faster performance, better security, and expanded functionality. As technology advances, older versions of StarRocks are gradually phased out. Using older versions of StarRocks can lead to challenges, bugs, and potential security and stability risks.
Distribution version lifecycle policy
For more information about the EMR Serverless StarRocks distribution versioning, see Version overview.
The Runtime Lifecycle Policy (RLP) defines the lifecycle of an EMR Serverless StarRocks distribution from its official release to its end of service. The following figure shows the RLP details for EMR Serverless StarRocks.
Milestone | Definition | Time point | Description |
General Availability (GA) | Official release | Month T | The version is officially released and can be used in a production environment. |
End of Service and Support (EOS) | Service and support termination | Month T + 2 years | New versions, including patch versions, are no longer released. During the EOS phase, services such as user Q&A, issue resolution, and Service-Level Agreement (SLA) compensation are suspended. |
If a version has a major bug that could cause significant issues, such as problems with data accuracy, security, or stability, StarRocks reserves the right to immediately stop new purchases of that version. Existing customers will be promptly notified to upgrade to a stable version. You must complete the version upgrade within the time specified in the notice to avoid business impact. Any business impact resulting from a failure to upgrade in time is not covered by the product's SLA.
For instances approaching End of Service (EOS), StarRocks notifies customers at least three months in advance and provides technical support to upgrade them to the latest stable version before the EOS date.
Version mappings and key lifecycle dates
The General Availability (GA) and End of Service (EOS) dates for each major version of EMR Serverless StarRocks are shown in the following table. Lifecycle management is based on major versions. All minor versions inherit the EOS date of their corresponding major version.
The EOS dates for some versions may be extended. For more information, see the description for each version.
Major version | GA | EOS | Description |
2.5 | Jan. 2024 | Jan. 2027 |
|
3.1 | Jan. 2024 | Jan. 2026 | New purchases are discontinued. We recommend using the latest version, 3.3. |
3.2 | Mar. 2024 | Dec. 2026 | This is a historical LTS version with integrated storage and computing. Its EOS date is extended to December 2026. |
3.3 | Dec. 2024 | Dec. 2026 | - |
Version overview
EMR Serverless StarRocks uses a two-tier versioning system with major and minor versions. This system helps you understand the product iteration pace and plan your upgrades. On the Instance Details page for a target instance in the StarRocks console, you can view the current version and available upgrade versions.
The following sections describe the version number structure, compatibility, and release methods.
Version types
Version type | Example | Description |
Major Version | 2.5, 3.2, 3.3 | The major version number is synchronized with the main version of the StarRocks community. It represents a major evolution of core features and architecture. |
Patch Version |
|
|
Version compatibility
Minor version compatibility (upgrade recommended)
Scope: All minor versions within the same major version are compatible.
Compatibility includes SQL syntax, client interfaces such as Java Database Connectivity (JDBC) and Open Database Connectivity (ODBC), table schemas, and data formats.
Compatibility is not guaranteed for program logic behavior, such as changes in specific query performance.
For the best stability and feature experience, we recommend that you upgrade to the latest minor version of your current major version.
Major version compatibility (upgrade with caution)
Full compatibility between major versions is not guaranteed. We try to maintain consistency in SQL syntax, interfaces, and behavior. However, because we follow the community's version evolution, the following changes may occur:
SQL syntax adjustments or deprecations
Interface changes or parameter adjustments
Changes in the default values of configuration items
Performance fluctuations caused by query execution plan optimizations
Before you upgrade, we recommend the following:
Review the version release notes to learn about new features and potential impacts.
Fully verify business compatibility in a test environment.
Avoid performing major version upgrades during peak business hours.
Version releases
StarRocks community documentation, such as StarRocks 3.3
Related services and notifications
To help you use Alibaba Cloud EMR Serverless StarRocks and plan your upgrades or migrations, we provide the following support:
Transparent lifecycle plan:
We create a detailed lifecycle plan for each StarRocks version. We communicate this information through official channels, such as product documentation and announcements.Advance notice for key milestones:
We notify you at least three months before key lifecycle milestones, such as end of support. Notifications are sent through company announcements, internal messages, emails, or text messages to give you enough time to prepare.Technical support and assistance:
When a product or version is about to be discontinued, we provide professional technical support. We help you assess job execution risks and explore viable solutions for a smooth business transition.
We are committed to providing an efficient and stable service experience. If you have any questions about version lifecycle management, contact our technical support team.