Sink data from RisingWave to MongoDB
This guide describes how to sink data from RisingWave to MongoDB. MongoDB is a document database designed for ease of application development and scaling. For more information, see MongoDB.
PUBLIC PREVIEW
This feature is in the public preview stage, meaning it’s nearing the final product but is not yet fully stable. If you encounter any issues or have feedback, please contact us through our Slack channel. Your input is valuable in helping us improve the feature. For more information, see our Public preview feature list.
Syntax
Parameters
Parameter Name | Description |
---|---|
mongodb.url | The URL of MongoDB. |
type | Defines the type of the sink. Options include append-only or upsert . |
collection.name | The collection name where data should be written to or read from. For sinks, the format is db_name.collection_name . Data can also be written to dynamic collections, see collection.name.field below for more information. |
collection.name.field | Optional. The dynamic collection name where data should be sunk to.
|
collection.name.field.drop | Optional. Controls whether the field value of collection.name.field should be dropped when sinking. Set this option to true to avoid the duplicate values of collection.name.field being written to the result collection. |
Data type mapping
MongoDB Type | RisingWave Type |
---|---|
Boolean | BOOLEAN |
32-bit integer | SMALLINT |
32-bit integer | INTEGER |
64-bit integer | BIGINT |
Double | REAL |
Double | DOUBLE |
Decimal128 | DECIMAL |
String | DATE |
String | VARCHAR |
String | TIME |
Date | TIMESTAMP WITHOUT TIME ZONE |
Date | TIMESTAMP WITH TIME ZONE |
String | INTERVAL |
Object | STRUCT |
Array | ARRAY |
Binary data | BYTEA |
Object | JSONB |
64-bit integer | SERIAL |
Examples
Below are some use cases for your reference.
Sink data with append-only
To create a sink with the append-only type:
In append-only mode, MongoDB will automatically generate an _id
field for each record, typically with a value of the ObjectId type. This is necessary because _id
is the primary key in MongoDB.
Sink data with upsert
To create a sink with the upsert type for a table with a single key:
Assuming the schema of t2
is:
name | type | pk |
---|---|---|
id | int | ✔ |
value | text |
Given the record:
id | value |
---|---|
1 | ’example of record’ |
The record written to MongoDB will be:
No redundant id
field will exist if the primary key of t2
is _id
.
The record written to MongoDB will be:
Dynamic collection name
Dynamic collection names are useful in certain scenarios. For example, a multi-tenant application may store its data using sharding, where tenant_id
is included as a prefix in the collection name, such as sharding_2024_01.tenant1_order
. This approach offers more flexibility and enables efficient data organization and retrieval based on specific tenant requirements.
To use a dynamic collection name:
collection.name
: Serve as a fallback collection name if the value ofcollection.name.field
is empty or null. In this case, it defaults todemo.t2
.collection.name.field
: Specify the field used for the collection name. This field must be of typevarchar
.collection.name.field.drop
: When set totrue
, it avoids duplicate values ofcollection.name.field
in the result collection.
Was this page helpful?