google-cloud-pubsub

I have been playing around with the Pub/Sub REST API on Google App Script. I have tried, without success, to create a subscriber with a push end point at script.google.com. The push end point URL was created with the StateTokenBuilder API , which requires a query parameter to be present on the end point URL. The query parameter is further used to forward any request at the URL to a javascript function inside the app. Is it allowed to have a push end point URL with a query parameter? However, even if it is allowed, I am unable to register for a push end point at the domain script.google.com. I

I'm experiencing a problem with GCP pubsub where a small percentage of data was lost when publishing thousands of messages in couple seconds. I'm logging both message_id from pubsub and a session_id unique to each message on both the publishing end as well as the receiving end, and the result I'm seeing is that some message on the receiving end has same session_id , but different message_id . Also, some messages were missing. For example, in one test I send 5,000 messages to pubsub, and exactly 5,000 messages were received, with 8 messages lost. The log lost messages look like this: MISSING

I need to import Pubsub_v1 and bigquery from google.cloud module. I have installed it and pip freeze shows below : gapic-google-cloud-pubsub-v1==0.15.4 google-cloud-bigquery==0.26.0 google-cloud-pubsub==0.27.0 proto-google-cloud-pubsub-v1==0.15.4 In my python script, i am importing the modules as below: import os from google.cloud import pubsub_v1 import time import json from google.cloud import bigquery The script is throwing error as : ImportError: cannot import name pubsub_v1 If i run $sudo pip install --upgrade google-cloud-pubsub then It is able to import pubsub but failing to import

Google did answer the question here https://cloud.google.com/pubsub/faq But I'm still unclear on which scenarios would each be used for? Is there something that pub sub can do which GCM can't? The primary difference between Google Cloud Pub/Sub and GCM is the points for scaling. GCM is designed to scale to many individual publishers and subscribers, on the order of end user devices such as phones. Cloud Pub/Sub, on the other hand, is designed to scale to very large throughput from/to fewer publishers and subscribers. The two could actually be used together. Imagine, for example, you were

I'm setting up a simple Proof of Concept to learn some of the concepts in Google Cloud, specifically PubSub and Dataflow. I have a PubSub topic greeting I've created a simple cloud function that sends publishes a message to that topic: const escapeHtml = require('escape-html'); const { Buffer } = require('safe-buffer'); const { PubSub } = require('@google-cloud/pubsub'); exports.publishGreetingHTTP = async (req, res) => { let name = 'no name provided'; if (req.query && req.query.name) { name = escapeHtml(req.query.name); } else if (req.body && req.body.name) { name = escapeHtml(req.body.name);