Use Pub/Sub as a Datastream destination

Google Cloud Serverless Applications
1

I was reading over some of the Datastream docs on creating streams and it mentions the following

However, you'll soon be able to create connection profiles for other destinations, including [BigQuery](https://cloud.google.com/bigquery) and [Pub/Sub](https://cloud.google.com/pubsub).

Is there a timeline on when Pub/Sub will be available as a destination? Secondly, do you know if there are any plans on supporting Pub/Sub message attributes when Pub/Sub does become available as a destination for Datastream? Thanks!

1 Like
2

We’re planning to make Pub/Sub destination available, but I can’t confirm specific features or timelines at this time.

3 Likes
3

Thanks!

4

What is the recommended work-around for now? Would it be to write data to Cloud Storage, and use a pub/sub subscription on Cloud Storage (https://cloud.google.com/storage/docs/pubsub-notifications)? That seems quite wasteful of resources.

3 Likes
5

Hi, We are looking forward to the support of Pub/Sub as a Datastream destination. Until then, the following article describes a good workaround.

https://cloud.google.com/datastream/docs/implementing-datastream-dataflow-analytics

6

@etaim hi! any updates on the timeline?

7

no updates at this time. please feel free to reach out to your account team, or create an issue in our public issue tracker to receive ongoing updates as they become available.

8

https://issuetracker.google.com/issues/278842503

for anyone who is likewise interested

4 Likes
9

Hi , Is pub sub available as destination for datastream in preview? if It is available then can you please provide me official documentation for that.

1 Like
10

It’s not available yet, and no ETA that we can share at this time.

1 Like
11

Okay,thanks for the info We are looking forward to the support of Pub/Sub as a Datastream destination.

12

I have a question regarding Datastream configuration. I’ve set up Datastream to write data to a GCS destination, which triggers a Cloud Function.

According to the documentation on Events and Streams, it states:

  • Update without Primary Key Changes: The change_type will be UPDATE.
  • Update with Primary Key Changes: The change_type will be UPDATE-INSERT.

However, in my case, I’m receiving Source-specific metadata where change_type is ‘UPDATE-INSERT’, even though the primary keys (‘account_id’ and ‘id’) are not changing.

For instance, the response I’m seeing includes ‘primary_keys’: [‘account_id’, ‘id’] and ‘change_type’: ‘UPDATE-INSERT’. Upon verifying the data flow in my table, these keys (‘account_id’, ‘id’) remain unchanged. Shouldn’t the change_type in this scenario be ‘UPDATE’ instead?

Could anyone advise on how to address this issue?

is there any alternate or workaround to get older value for updating field without primary key?

13

@etaim any news on this? Pub/Sub as a datastream destination would be a great feature to have

1 Like
14

It has been 3 years since this comment. Any progress in making pub/sub available as a destination? :slightly_smiling_face: