Use the SQL statement below to connect RisingWave to Google Pub/Sub source.
Field | Note |
---|---|
pubsub.subscription | Required. Specifies where the Pub/Sub subscription to consume messages from. Pub/Sub is used to load-balance messages among all readers pulling from the same subscription, so one subscription (i.e., one source) can only be used for one materialized view (MV) that is shared between the actors of its fragment. Otherwise, different MVs on the same source will both receive part of the messages. |
pubsub.credentials | Required. A JSON string containing the service account credentials for authorization, see the service-account credentials guide. The provided account credential must have the pubsub.subscriber role and pubsub.viewer role. |
pubsub.start_offset.nanos | Optional. Cannot be set together with pubsub.start_snapshot . Specifies a numeric timestamp in nanoseconds, ideally the publish timestamp of a message in the subscription. If present, the connector seeks the subscription to the timestamp and starts consuming from there. Note that the seek operation is subject to limitations based on the message retention policy of the subscription. |
pubsub.start_snapshot | Optional. Cannot be set together with pubsub.start_offset.nanos . If present, the connector first seeks to the specified snapshot before starting consumption. |
pubsub.parallelism | Optional. Specifies the number of parallel consumers to run for the subscription. If not specified, the default value is 1. |