This topic describes the announcements of Realtime Compute for Apache Flink, including version updates, feature updates, and product activities.
Alibaba Cloud Realtime Compute (Blink) has entered the product convergence period. Download the PDF file to view the details.
Alibaba Cloud Realtime Compute (Blink) has entered the product convergence period. For more information about Alibaba Cloud Realtime Compute (Blink), see Service types. For more information about Alibaba Cloud Realtime Compute (Blink), download the Blink Exclusive Mode (Phased-Out for Alibaba Cloud) file to view the details.
November 15, 2022: Blink exclusive clusters enter the EOM2 stage
Blink exclusive clusters of Realtime Compute for Apache Flink enter the EOM2 stage from November 15, 2022. EOM is short for end of marketing. At the EOM2 stage, orders for new purchases and scaling of existing Blink exclusive clusters are not accepted, and the renewal period that is specified in renewal orders cannot exceed four months. This aims to provide a more comprehensive service system, focus on meeting customer requirements, and provide a clearer and more simplified experience of using Realtime Compute for Apache Flink. Alibaba Cloud service support for Blink exclusive clusters are retained. For more information about the lifecycle policies and the time point for the end of service (EOS) of Blink exclusive clusters, see Lifecycle policies and Service types.
Realtime Compute for Apache Flink launches the fully managed Flink service. This service provides better and more comprehensive real-time data processing capabilities. Fully managed Flink allows you to use multiple development methods such as user-defined functions (UDFs) or JAR instead of using only SQL statements. The development costs are not increased.
Thank you for your support for Realtime Compute for Apache Flink.
August 15, 2022: Blink shared clusters enter the EOM2 stage
Blink shared clusters of Realtime Compute for Apache Flink enter the EOM2 stage from August 15, 2022. At the EOM2 stage, orders for new purchases and scaling of existing Blink shared clusters are not accepted, and the renewal period that is specified in renewal orders cannot exceed four months. This aims to provide a more comprehensive service system, focus on meeting customer requirements, and provide a clearer and more simplified experience of using Realtime Compute for Apache Flink. Alibaba Cloud service support for Blink shared clusters are retained. For more information about the lifecycle policies and the time point for the EOS of Blink shared clusters, see Lifecycle policies and Service types.
Realtime Compute for Apache Flink launches the fully managed Flink service. This service provides better and more comprehensive real-time data processing capabilities. Fully managed Flink allows you to use multiple development methods such as UDFs or JAR instead of using only SQL statements. The development costs are not increased.
Thank you for your support for Realtime Compute for Apache Flink.
April 28, 2021: Realtime Compute for Apache Flink in exclusive mode is no longer available
Realtime Compute for Apache Flink in exclusive mode is no longer available starting from April 28, 2021. You can only scale out, scale in, or renew the existing projects of Realtime Compute for Apache Flink in exclusive mode. If you want to purchase Realtime Compute for Apache Flink, we recommend that you purchase fully managed Flink.
Announcement on the version update of Realtime Compute for Apache Flink jobs due to the change of endpoints of Message Queue for Apache RocketMQ
Update announcement
Region-based endpoints are used to access Message Queue for Apache RocketMQ. For more information, see Announcement on the settings of internal TCP endpoints. If you use the Message Queue for Apache RocketMQ connector in Realtime Compute for Apache Flink of a version earlier than Blink 3.7.10, you must update the version of your Realtime Compute for Apache Flink job to Blink 3.7.10 or later and change the endpoint that you specified in the job to the new endpoint of Message Queue for Apache RocketMQ. For more information about endpoints, see the following topics:
Usage notes
The old endpoints of Message Queue for Apache RocketMQ is unavailable starting from November 2021. If you still use the old endpoints, the stability of jobs may be affected. To prevent this issue, we recommend that you update the version of your Realtime Compute for Apache Flink jobs before November 2021.
The product team of Message Queue for Apache RocketMQ ensures that the old endpoints of Message Queue for Apache RocketMQ remain effective before November 2021. However, the stability of jobs that use the old endpoints may be affected.
This update can cause the states of jobs to change. To minimize the impact of the update on your business, we recommend that you update the version of your jobs at an appropriate time based on your business requirements.
After November 1, 2021, the product team of Realtime Compute for Apache Flink no longer maintains and supports jobs that use the old endpoints of Message Queue for Apache RocketMQ.
From 21:00 on August 10, 2020 to 02:00 on August 11, 2020: Realtime Compute for Apache Flink is updated
Realtime Compute for Apache Flink in exclusive mode in the China (Hangzhou) region is updated. Services are not interrupted during the update, but you cannot create clusters or scale in or out clusters.
From 21:00 on April 28, 2020 to 02:00 on April 29, 2020: Realtime Compute for Apache Flink is updated
Realtime Compute for Apache Flink in exclusive mode in the China (Shanghai) region is updated. Services are not interrupted during the update, but you cannot scale in or out clusters.
From April 20, 2020 to April 22, 2020: The storage service is updated
The storage service of Realtime Compute for Apache Flink in shared mode in the China (Shanghai) and China (Shenzhen) regions is updated. This update improves the stability of Realtime Compute for Apache Flink. In most cases, this update does not affect your services. In special circumstances, jobs of Blink 3.2 and Blink 3.3 fail and then restore to normal during the update.
August 27, 2019: The Configurations tab is added
The Configurations tab is added to the right side of the Development page in the Realtime Compute for Apache Flink console. The link to resource configurations is removed from the Basic Properties tab.
May 30, 2019: New features in Realtime Compute for Apache Flink versions later than V3.0.0 are released
Overview
The vertex information can be queried. For more information, see Overview.
Metrics
The curve charts that display the auto scaling metrics are added. For more information, see Metrics.
Timeline
The Timeline tab is added to the Administration page. For more information, see Timeline.
Properties and parameters
Details about auto scaling iterations can be queried. For more information, see Properties and parameters.
January 24, 2019: Blink 2.2.7 is released
Among all Blink 2.X
versions, Blink 2.2.7
is the latest stable version. Compared with Blink 1.X versions, Blink 2.2.7 has significant improvements. Among all Blink 1.X versions, Blink 1.6.4
is the latest stable version. Blink 2.2.7 uses the new generation of Niagara as the data storage system for the state backend platform. Blink 2.2.7 also optimizes SQL performance and introduces a wide range of new features.