Highlights of RisingWave v1.6: The Open-Source Distributed SQL Streaming Database

GCS source

Google Cloud Storage is a cloud-based object storage service that allows you to store and retrieve data. Like with other source connectors in RisingWave, you can establish a connection between RisingWave and GCS to start consuming data by using the CREATE SOURCE or CREATE TABLE command.

CREATE TABLE gcs( 

    id int,

    name varchar

) WITH (

    connector = 'gcs',

    match_pattern = '%Ring%*.ndjson',

    gcs.bucket_name = 'example-source',

    gcs.credential = 'xxxxx',

    gcs.service_account = 'xxxxx'

) FORMAT PLAIN ENCODE JSON;

StarRocks sink

StarRocks, formerly Palo, is an open-source analytical database well-suited for real-time analytics and interactive query processing. To sink data from RisingWave to StarRocks, use the CREATE SINK command. Note that the StarRocks sink connector cannot sink struct and json types as StarRocks’s stream load does not support these data types.

CREATE SINK starrocks_sink

FROM mv WITH (

    connector = 'starrocks',

    type = 'append-only',

    starrocks.host = 'starrocks-fe',

    starrocks.mysqlport = '9030',

    starrocks.httpport = '8030',

    starrocks.user = 'users',

    starrocks.password = '123456',

    starrocks.database = 'demo',

    starrocks.table = 'demo_bhv_table',

    force_append_only='true'

);

For more details see:

SSL related configurations

This version update provides two new ways for you to alter SSL settings during the session, granting you more flexibility.

First, we added the properties.ssl.endpoint.identification.algorithm parameter for Kafka source and sink, which allows you to bypass the verification of CA certificates. This parameter is worth looking into if you are running into a “SSL handshake failed error” when creating a Kafka source or sink.

We also introduce the RW_SSL_CERT and RW_SSL_KEY environment variables, which are used to specify the SSL certificate and the key file location for frontend nodes, respectively.

For more details see:

Temporal filter enhancements

Temporal filters selects or excludes data based on time-related criteria, such as timestamps or date ranges. These filters are invaluable when you want to create small windows for your unbounded data. RisingWave already supports temporal filters, but this update introduces some new features, which allow you to construct more complex temporal filters.

Previously, simple comparisons were supported, only allowing you to compare the data to a specific date or the current time, where NOW() could not be the upper bound.

Now, temporal filters allow for NOW() to be the upper bound condition and allows you to connect a temporal filter to a normal condition using the OR operator. However, connecting multiple temporal filters together using the OR operator is not supported.

t > NOW() - INTERVAL '1 hour' OR t IS NULL 

t + INTERVAL '5' SECOND < NOW()

More temporal filter enhancements are in the works so stay tuned for future releases!

For more details see:

CONCLUSION

These are just some of the new features included with the release of RisingWave v1.6. To see the entire list of updates, which includes more SQL features, connector updates, including changes to the Elasticsearch sink connector, please refer to the detailed  to stay up to date on the newest features and planned releases.