> ## Documentation Index
> Fetch the complete documentation index at: https://docs.streamnative.io/llms.txt
> Use this file to discover all available pages before exploring further.

# RisingWave

> Understand the managed RisingWave engine, its query interfaces, persistence model, and SQL reference.

RisingWave is the only SQLWorkspace engine supported during Private Preview. The SQLWorkspace engine model is pluggable, but you cannot currently select or replace the engine.

StreamNative deploys and operates RisingWave in the placement selected for your SQLWorkspace. RisingWave executes PostgreSQL-compatible SQL over streaming data and maintains continuously updated computations such as materialized views.

## Engine model

The managed engine includes the services required to accept SQL, execute streaming computations, coordinate metadata, and compact persistent state. StreamNative configures, deploys, and monitors these services as one SQLWorkspace engine.

RisingWave uses two managed persistence resources:

<CardGroup cols={2}>
  <Card title="Metadata Store" icon="database" href="/sql/overview/engine/metadata-store">
    Stores engine metadata in Amazon RDS for PostgreSQL.
  </Card>

  <Card title="Object Storage" icon="box-archive" href="/sql/overview/engine/object-storage">
    Stores durable streaming state in Amazon S3.
  </Card>
</CardGroup>

<Note title="AWS support">
  During Private Preview, managed metadata and object storage are supported only for SQLWorkspace placements on AWS. Other cloud providers are not currently supported.
</Note>

## Query interfaces

You can submit SQL to the same engine through either interface:

| Interface                        | Use case                                                          |
| -------------------------------- | ----------------------------------------------------------------- |
| **SQL Studio**                   | Run and inspect queries in the StreamNative Cloud Console.        |
| **Native PostgreSQL connection** | Connect a PostgreSQL-compatible client, such as `psql`, over TLS. |

PostgreSQL wire compatibility does not mean that every PostgreSQL server feature is available. RisingWave syntax, system catalogs, extensions, and SQL behavior can differ from PostgreSQL.

## Work with managed topic sources

StreamNative periodically discovers eligible topics from a SQLCatalog and creates missing source objects in its engine database. Always reference topic-derived schema and source names with double-quoted identifiers. This example uses a Pulsar topic in `public/default`:

```sql theme={null}
SELECT *
FROM "public/default"."orders-topic"
LIMIT 100;
```

Create tables or materialized views for subsequent transformations and continuously maintained results:

```sql theme={null}
CREATE MATERIALIZED VIEW orders_by_status AS
SELECT status, COUNT(*) AS order_count
FROM "public/default"."orders-topic"
GROUP BY status;
```

## RisingWave documentation

* [Source, Table, Materialized View, and Sink](https://docs.risingwave.com/get-started/source-table-mv-sink) explains the roles of RisingWave's core SQL objects.
* [Data processing in RisingWave](https://docs.risingwave.com/processing/overview) introduces ad hoc queries and continuously maintained streaming computations.
* [CREATE MATERIALIZED VIEW](https://docs.risingwave.com/sql/commands/sql-create-mv) provides the complete materialized-view syntax and behavior.
* [Joins](https://docs.risingwave.com/processing/sql/joins) covers RisingWave join patterns.

Use the documentation that corresponds to the RisingWave version provided by your SQLWorkspace when behavior is version-specific.