Ad-hoc Queries and Visualization
Like traditional databases, RisingWave can store data and allow users to perform ad-hoc queries on it. However, it's important to note that the source in RisingWave does not persist data, and RisingWave does not support directly quering the source, unless it's from Kafka. The main reason relates to data ownership, data consistency, and performance issues. Interested readers can refer to the discussion in previous article.
| Functions | Tables | Sources | Materialized Views |
|---|---|---|---|
| Support ad-hoc queries ( select statement) | yes | no | yes |
| Support streaming queries ( create materialized view statement) | yes | yes | yes |
In production environments, RisingWave is widely used for real-time reporting. Users can utilize a variety of reporting tools, such as Apache Superset, Grafana, etc., to interface with RisingWave.
If the reporting tool you are using is not listed in the official RisingWave documentation, you can also attempt to connect to RisingWave directly using the PostgreSQL interface. Because RisingWave is compatible with the PostgreSQL wire protocol, most systems within the PostgreSQL ecosystem are likely able to communicate with RisingWave directly.