Join us in exploring some of the most prominent features highly anticipated in this new release, such as watermarks, the emit-on-window-close policy, read-only transactions, new window functions, and more.
We are thrilled to announce the new release of RisingWave: the Rust-written, open-source streaming database. RisingWave v1.1 is packed with many exciting new features. Here are the key highlights.
Real-time data ingestion is inherently unordered. To properly handle out-of-order events, we need watermarks.
Accordingly we introduce watermarks in this release. In RisingWave, you can define watermarks in sources and append-only tables. Once you define them, you can use them in time-window aggregations and other stateful operations.
Append-only tables is also a new feature that was introduced in this version to facilitate the definition of watermarks.
For details about watermarks, see Watermarks.
For windowed calculations, we offer the flexibility to emit results either upon update or when the window closes.
Emitting results upon window close is particularly advantageous in certain situations.For example, when writing to append-only downstream systems like Kafka or S3, or when dealing with calculations that benefit from triggering only when the window closes, such as percentile calculations.
Our emit-on-window-close policy, introduced in v1.1, caters to these scenarios.
For details about this policy, see Emit on window close.
We recognize the significance of transactions in ensuring data processing consistency and reliability.
In this release, so we have incorporated support for read-only transactions. All reads within a transaction are executed against the consistent snapshot, guaranteeing data consistency as they originate from the same point-in-time.
For details about Read-only transactions, see Transactions.
To enhance your data analysis capabilities, we have introduced several new window functions in RisingWave v1.1. These include lead(), lag(), first_value(), and last_value().
For details about new window functions, see Window functions.
Conclusion
These features are just a glimpse of the many exciting additions in RisingWave v1.1. For a comprehensive overview, please refer to the detailed release notes.
As we approach the 2,000th community member, we anticipate even more remarkable progress and success in our mission to revolutionize stream processing for the benefit of all.
Sign up for our monthly newsletter if you’d like to keep up to date on all the happenings with RisingWave. Follow us on Twitter and Linkedin, and join our Slack community to talk to our engineers and hundreds of streaming enthusiasts worldwide.
RisingWave is a cutting-edge SQL database designed to streamline the processing, analysis, and management of real-time event streaming data. But what sets it apart from other databases? Let’s take a look at the top 12 features, as ranked by our users in a recent survey, that make RisingWave a go-to choice for handling the complexities of real-time data.
Is it possible to implement a proactive agent which is able to know what to do without instructions from human? To achieve that, the agent needs to know what’s happening in real-time.
In this article, we'll show you how to set up a continuous data pipeline that seamlessly captures changes from your Postgres database using Change Data Capture (CDC) and streams them to Apache Iceberg.
