In April, we blossomed with the season, since April marks not just the arrival of spring, but also the celebration of our birthday. On April 8, two years ago, we open-sourced RisingWave! We continue to steadily grow and have released RisingWave v1.8 earlier this month. At the same time, we continue to please our cloud users with new features and functionalities, month after month. But that’s not all we do—our April doings extended over many fronts. To learn more about it, scroll below.
????♀? Surf RisingWave! ????♂?
- Source and sink status. To improve observability, we brought back the source and sink page to the cluster detail page. For each source or sink, we summarize the metadata, the running throughout, and the error logs associated with this source or sink together on this page.
- Service account and API key. We introduced a service account as a special type of account designed for programmatic applications. The organization admin can now create a service account and then add an API key for authentication usage.
- Metrics export. We enable enterprise customers to export the monitoring metrics of their RisingWave clusters from RisingWave Cloud into their monitoring stacks.
- Terraform module. We have developed the Terraform module for managing resources in RisingWave Cloud. For more information on how to integrate RisingWave Cloud with your existing IaC framework, please read this.
- MongoDB direct CDC: It eliminates the need for intermediate tunnels via Kafka/ Debezium which simplifies data flow and improves the end-to-end data latency.
- OAuth authentication: It allows for the integration of external authentication providers with RisingWave. This enables users to authorize access to RisingWave using their existing authentication infrastructure.
- SQL Meta Backend (Technical Preview): We introduced a technical preview of our new SQL meta backend, which addresses the scalability and flexibility limitations of our previous Etcd backend.
- ALTER SOURCE <name> REFRESH SCHEMA: We introduced a new command that enables users to effortlessly refresh a source or a table with the latest schema. This is achieved by retrieving the latest schema from the Confluent Schema Registry and applying schema changes automatically, like a syntactic sugar to ALTER SOURCE <name> ADD COLUMN ...;.
- End-to-end support for Iceberg-based analytics: We now provide beta support for batch reads on Iceberg, offering users the ability to merge real-time results from RisingWave with historical data stored in Iceberg.
