Hologres versions follow a defined lifecycle from General Availability (GA) to End of Service (EOS). Understanding this lifecycle helps you determine whether your current version is still supported, plan upgrades before service is discontinued, and evaluate compatibility risks. Notifications are sent at least three months before any milestone date.
Lifecycle phases
Each Hologres version goes through two phases:
| Milestone | Full name | Phase timeline | What it means |
|---|---|---|---|
| GA | General Availability | Month T | The version is officially released and supported for use in production environments. |
| EOS | End of Service | Month T + 2 years | No new versions or patch versions are released. Technical support, issue resolution, and Service-Level Agreement (SLA) compensation are discontinued. |
No phase starts earlier than its scheduled date. The start date is announced through official notification channels at least three months in advance.
What happens after EOS
When a version reaches EOS, Hologres Operations and Maintenance (O&M) may take the following actions:
Emergency upgrades: If a version has a critical bug — such as a security issue or data inaccuracy — Hologres O&M reserves the right to perform an emergency upgrade to a compatible patched version within the same major version.
Stability-driven upgrades: If an instance poses a potential stability risk to you or the entire cluster, Hologres O&M reserves the right to upgrade the instance during an O&M window to a stable version within its GA period.
To view the current version and available upgrade versions for an instance, go to the Instance Details page in the Hologres console. For details, see Common errors during upgrade preparation.
Version numbers and their meanings
Hologres version numbers follow a Major.Minor format.
| Version component | What changes | Upgrade example |
|---|---|---|
| Major | Fundamental changes and new features. Incremented based on the size and scale of the changes. | 1.1.21 to 1.3.38 (Major: 1.1 to 1.3) |
| Minor | Quality improvements and bug fixes for existing features. Incremented when multiple improvements are added. | 1.3.24 to 1.3.38 (Minor: 24 to 38) |
Version lifecycle dates
The following table lists the GA and EOS dates for each Hologres major version. Versions with an EOS date in the past no longer receive technical support or SLA compensation.
| Major version | GA | EOS |
|---|---|---|
| 0.7 | 2020-04 | 2022-04 |
| 0.8 | 2020-10 | 2022-10 |
| 0.9 | 2021-01 | 2023-01 |
| 0.10 | 2021-05 | 2023-05 |
| 1.1 | 2021-10 | 2023-10 |
| 1.3 | 2022-07 | 2024-07 |
| 2.0 | 2023-04 | 2025-04 |
| 2.1 | 2023-10 | 2025-10 |
| 2.2 | 2024-04 | 2026-04 |
| 3.0 | 2024-07 | To be determined |
| 3.1 | 2025-06 | To be determined |
| 3.2 | 2025-06 | To be determined |
| 4.0 | 2025-09 | To be determined |
Compatibility
Between minor versions (same major version)
Hologres guarantees compatibility between minor versions within the same major version. This covers SQL syntax, interfaces, and the engine framework. It does not cover business logic or data processing.
Upgrade to the latest minor version within your current major version to stay compatible.
Between major versions
Hologres does not guarantee compatibility between major versions. Alibaba Cloud makes every effort to maintain compatibility of program logic, SQL syntax, and interfaces across major versions. Any known incompatibilities are communicated through documentation or after-sales service.
Bug fixes
To get bug fixes for your version, upgrade to a later major or minor version in accordance with the compatibility policy above.
Example: If your instance runs version 1.1.33 and the latest version is 1.3.40, upgrade to 1.3.40 or later.
Feature releases and bug fixes are announced in Release notes.
Notifications and support commitments
Before a version's EOS date, Hologres will:
Notify you at least three months in advance. Notifications are sent to the root account that purchased the product through official website announcements, product documentation announcements, internal messages, emails, and text messages. To receive these notifications, subscribe to product update messages in the Message Center.
Assess operational risks with you. Hologres will help you evaluate job-related operational risks and discuss upgrade paths before the version's service is stopped.
After a version reaches EOS, Hologres O&M will proactively upgrade instances where stability is affected, to a stable version within its GA period.
What's next
Check your current instance version on the Instance Details page in the Hologres console.
Review Release notes for the latest features and bug fixes in each version.
See Common errors during upgrade preparation before starting an upgrade.