Skip to content

Commit 721e9cb

Browse files
committed
RisingWave: Improve wording. Remove exaggerations.
1 parent 89d3a6f commit 721e9cb

File tree

1 file changed

+1
-6
lines changed

1 file changed

+1
-6
lines changed

docs/integrate/risingwave/index.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,11 +13,6 @@ results are materialized.
1313
It provides both a Postgres-compatible SQL interface, like CrateDB,
1414
and a DataFrame-style Python interface.
1515

16-
RisingWave can ingest millions of events per second, continuously join
17-
and analyze live streams with historical data, serve ad-hoc queries at
18-
low latency, and persist fresh, consistent results to Apache Iceberg™
19-
or any other downstream system.
20-
2116
![RisingWave overview](https://github.com/user-attachments/assets/5bd27415-300d-4b8a-aa47-196eed041ed7){h=200px}
2217

2318
> Deliver fresh, low-latency insights from real-time streams,
@@ -74,7 +69,7 @@ CREATE TABLE public.average_sensor_readings (
7469
:::{note}
7570
The standard approach with RisingWave would be to use its [CREATE SINK] operation
7671
to connect to an external target.
77-
However, because this does not work with CrateDB, a little Python event processor
72+
However, because this does not currently support CrateDB, a little Python event processor
7873
is needed to relay the data. An example implementation can be found in the tutorial
7974
referenced below.
8075
:::

0 commit comments

Comments
 (0)