This topic describes the versioning scheme, version mapping, and product lifecycle policy for EMR Serverless StarRocks.
Background information
As the StarRocks open-source community evolves, new versions offer faster performance, enhanced security, and more features. As technology advances, older versions are gradually phased out. If you continue to use an older version of StarRocks, you may face various challenges, encounter defects, and even expose your system to security and stability risks.
Runtime lifecycle policy
For details about the EMR Serverless StarRocks versioning scheme, see Version overview.
The Runtime Lifecycle Policy (RLP) describes the lifecycle of an EMR Serverless StarRocks version from General Availability (GA) to End of Service and Support (EOS). The RLP of EMR Serverless StarRocks is shown in the following figure.
|
Milestone |
Definition |
Timeline |
Description |
|
General Availability (GA) |
General Availability (GA) |
Month T |
The version is officially released and ready for production use. |
|
End of Service and Support (EOS) |
End of Service and Support (EOS) |
Month T + 2 years |
The version no longer receives new releases, including patch versions. During the EOS phase, services such as technical support, issue resolution, and SLA compensation are discontinued. |
-
If a version has a critical defect that can cause significant customer impact (for example, data correctness issues, security vulnerabilities, or severe stability issues), StarRocks reserves the right to immediately suspend new subscriptions for that version and promptly notify existing customers to upgrade to a stable version. You must complete the upgrade within the specified time to avoid business impact. Business impact caused by failing to upgrade on time is not covered by the product's SLA.
-
For an instance running a version that is approaching its EOS date, StarRocks will notify you at least three months in advance to assist with upgrading to the latest stable version before the EOS date.
Version mapping and lifecycle dates
The following table lists the General Availability (GA) and End of Service and Support (EOS) dates for each major version of EMR Serverless StarRocks. Lifecycle management is based on major versions, and all corresponding patch versions inherit the EOS date of their major version.
In special cases, the EOS date for some versions is extended. For details, see the description for each version.
|
Major version |
GA |
EOS |
Description |
|
2.5 |
2024-01 |
2027-01 |
|
|
3.1 |
2024-01 |
2026-01 |
This version is no longer available for new purchases. We recommend using the latest 3.3 version. |
|
3.2 |
2024-03 |
2026-12 |
A legacy Long-Term Support (LTS) version with integrated storage and computing. The EOS date is extended to December 2026. |
|
3.3 |
2024-12 |
2026-12 |
- |
Version overview
EMR Serverless StarRocks uses a two-tier versioning system of major and patch versions to help you understand the product iteration cycle and plan upgrades. The Instance Details page for the target instance in the StarRocks console shows the current version and available upgrade versions.
The following sections describe the version structure, compatibility, and release information.
Version types
|
Version type |
Example |
Description |
|
Major version |
2.5, 3.2, 3.3 |
Major versions align with the StarRocks open-source community mainline and often introduce significant changes to core features and architecture. |
|
Patch version |
|
|
Version compatibility
Patch version compatibility (Upgrade recommended)
-
Scope: All patch versions within the same major version are compatible.
-
Compatible content: SQL syntax, client interfaces (JDBC/ODBC), table schemas, and data formats.
-
Compatibility is not guaranteed for the following: behavior of application logic, such as changes in the performance of specific queries.
-
Recommendation: To ensure optimal stability and access the latest features, we recommend upgrading to the latest patch version within your current major version.
Major version compatibility (Upgrade with caution)
-
Description: Full compatibility between major versions is not guaranteed. Although we strive to maintain consistency in SQL syntax, interfaces, and behavior, the following changes may occur due to evolution in the community version:
-
SQL syntax adjustments or deprecation
-
Interface changes or parameter adjustments
-
Changes in the default values of configuration items
-
Performance fluctuations due to optimizations in the query execution plan
-
-
Upgrade recommendations:
-
Before upgrading, review the release notes to understand new features and potential breaking changes.
-
Fully validate business compatibility in a test environment.
-
Avoid performing major version upgrades during peak business hours.
-
Version releases
-
StarRocks community documentation, for example, StarRocks 3.3
Related services and notifications
We provide the following support services to help you use EMR Serverless StarRocks more effectively and plan your upgrades or migrations:
-
Transparent lifecycle plans:
We define a detailed lifecycle plan for each StarRocks version and publish it through official channels such as product documentation and announcements. -
Advance notice for key milestones:
Before a key milestone, such as the End of Service and Support (EOS) date, we provide at least three months' advance notice through official announcements, internal messages, emails, or SMS messages, giving you ample time to prepare. -
Technical support and assistance:
When a product or version nears its end of service, we provide professional technical support. We help you assess job execution risks and work with you on a practical plan 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.