This topic provides service notices of Realtime Compute for Apache Flink, including version updates, feature updates, and product activities.

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 and ticket service 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. Realtime Compute for Apache Flink also provides a complete migration tool to help you complete data migration.

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 and ticket service 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. Realtime Compute for Apache Flink also provides a complete migration tool to help you complete data migration.

Thank you for your support for Realtime Compute for Apache Flink.

November 1, 2021: The endpoints of Message Queue for Apache RocketMQ are unavailable and Realtime Compute for Apache Flink jobs need to be updated to adapt to the change

  • Update notice
    The endpoints that are used to access Message Queue for Apache RocketMQ in specific regions are changed. For more information, see Announcement on the settings of internal TCP endpoints. If you already use the Message Queue for Apache RocketMQ connector in Realtime Compute for Apache Flink that is deployed in Ververica Runtime (VVR) of a version earlier than 3.0.1, you must update the VVR version of your Realtime Compute for Apache Flink job to 3.0.1 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:
  • Precautions
    • The outdated endpoints of Message Queue for Apache RocketMQ are unavailable from November 2021. If you use outdated endpoints, the stability of your business 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 outdated endpoints of Message Queue for Apache RocketMQ remain available before November 2021. However, the stability of the jobs that use outdated 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 your jobs during off-peak hours.
    • After November 1, 2021, the product team of Realtime Compute for Apache Flink no longer maintains and supports jobs that use outdated endpoints of Message Queue for Apache RocketMQ.

September 15, 2020: The public preview of fully managed Flink is complete and fully managed Flink becomes available for commercial use

Fully managed Flink becomes available for commercial use after the public preview is complete on September 15, 2020. To ensure seamless migration of your business, we recommend that you evaluate the impact of this change on your business in advance. For users who apply for the public preview of fully managed Flink for a long period of time, the service can be used free of charge until 23:59:59 on September 30, 2020.

For more information about the pricing of commercial products, see Billing unit and billable items. If you have questions, submit a ticket to consult the issue.

From 21:00:00 on July 23, 2020 to 24:00:00 on July 23, 2020: Fully managed Flink is updated

The console of fully managed Flink is updated from 21:00:00 on July 23, 2020 to 24:00:00 on July 23, 2020. When an update is being performed, you cannot use the console. If you require assistance, submit a ticket.