VVR 11.x and later follow a three-part versioning scheme. This document describes the version number format, release policies, and compatibility guarantees to help you plan upgrades and maintain job reliability.
Version number format
VVR 11.x and later use the format [Major version].[Minor version].[Bugfix version].
| Version component | Meaning | Upgrade impact |
|---|---|---|
| Major version | Breaking feature changes, incompatible API modifications, or substantial architectural shifts. Follows Apache Flink's major version updates. | May require migration efforts in your applications. |
| Minor version | New, backward-compatible features. Does not affect existing features or require additional adaptation. | None. Major and minor version numbers are the primary considerations when selecting an engine version. |
| Bugfix version | Fixes for urgent bugs such as widespread data disorder, data loss, or job instability. Not displayed in the console. Does not require manual updates. | None. Details are published in Realtime Compute for Apache Flink's Maven central repository. |
Version release policy
| Version type | Announcement channel | Action required |
|---|---|---|
| Minor version | Release notes published on the service website and user community, covering feature details and usage instructions. | None. Review release notes to learn about new features. |
| Bugfix version | Announcement prominently displayed in the console, indicating an urgent bug fix. | Restart running jobs to apply the fix. |
Version compatibility
Minor versions are backward compatible, guaranteeing consistent functionality and data compatibility. Upgrading to a new minor version does not introduce compatibility issues.
Supplemental information
The versioning policy for VVR 11.x and later is effective upon its release. We will announce any subsequent adjustments or updates through our official channels. For any questions or suggestions, contact our support team.