---
title: "Discussion on \"How RisingWave Handles Late-Arriving Data and Watermarks\" | Hashnode"
description: "Discussion on \"How RisingWave Handles Late-Arriving Data and Watermarks\". A deep dive into watermark semantics in RisingWave: how to declare them, how late data is handled, and how the model compares to Apache Flink."
url: "https://hashnode.com/posts/late-arriving-data-watermarks-risingwave/6a10c6b4029687802a887e9c"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How RisingWave Handles Late-Arriving Data and Watermarks](https://risingwave.com/blog/late-arriving-data-watermarks-risingwave?utm_source=hashnode&utm_medium=feed)

A deep dive into watermark semantics in RisingWave: how to declare them, how late data is handled, and how the model compares to Apache Flink.

May 22 · 8 min read · risingwave.com  
Read the article

-   [#watermarks](https://hashnode.com/tag/watermarks)
-   [#stream-processing](https://hashnode.com/tag/stream-processing)
-   [#event-time](https://hashnode.com/tag/event-time)
-   [#risingwave](https://hashnode.com/tag/risingwave)
-   [#flink](https://hashnode.com/tag/flink)

## Written by

[Yuhao Su](https://hashnode.com/@yuhao)

@yuhao

  
[View profile](https://hashnode.com/@yuhao)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
