Cloud Pub/Sub

Welcome to the Google Cloud Pub/Sub idea forum. You can submit and vote on ideas here to tell the Pub/Sub team which features you’d like to see.

This forum is for feature suggestions. If you’re looking for help forums, look here:

We can’t wait to hear from you!

  1. Python client library as on today is not working in an environment where http_proxy is not set

    Following error is occuring:

    E0624 07:18:51.447702419 9603 uriparser.cc:46] bad uri.scheme: ''
    E0624 07:18:51.447727494 9603 uri
    parser.cc:52] ^ here
    E0624 07:18:51.447734361 9603 httpproxy.cc:54] cannot parse value of 'httpproxy' env var

    ===
    Client Library version:

    google-cloud-pubsub 0.35.4

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  2. Cloud pubsub emulator does not handle 202 response code correctly on push endpoints.

    Small discrepancy between the emulator and the production Cloud Pub/Sub.

    When responding to a push subscription with http code 202 the emulator will output the following message:

    [pubsub] INFO: Failed to push to endpoint '<endpoint here>': Fetched url '<url here>' but got a response code that is not an acknowledgement: 202

    Whereas per existing Cloud Pub/Sub documentation this should be considered a valid ack response for push endpoints:

    https://cloud.google.com/pubsub/docs/push

    (I haven't explicitely tested other response codes but I'm fairly certain that 204 and 200 are correctly handled, didn't test 201 and 102.)

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  3. Emulator should not need content-type header, or provide proper error response

    The real PubSub API request a publish request (potentially others) without the content-type header.

    The PubSub Emulator returns a 404 error if no content-type header is set, or a wrong content-type header is set.

    404 is the wrong HTTP status code in such a situation (400 is correct), and without a proper error message, this is extremely difficult to debug. I wasted a lot of time debugging whether I set up the topic correctly, and whether I constructed the URL correctly.

    Please either ignore the content-type header (like the PubSub API does), or provide a 400 response with a proper…

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  4. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  5. No esta traducida al español.

    No esta traducida al español.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add asyc messages on standard env

    Using the standard environment with automatic scaling (no background threads) there are no or very small chances to buffer messages and send them to pub/sub in a batch rather than one by one (e.g triggered by a client request).

    I would like to see it possible to buffer messages and have the pub sub lib send them either when the buffer is full or after a certain time interval has been reached.

    This would be a very nice performance boost.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  7. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  8. Emulator needs to increase max gRPC message size to match production

    The emulator drops connections when publish messages exceed 4 MiB. However, the production pubsub service enforces a max publish message size limit of 10000000 bytes. It returns a friendly error code when you exceed that limit (at least up to some max; I haven't really tried). The two should match.

    The server needs to call maxInboundMessageSize() when it is being configured:

    https://grpc.github.io/grpc-java/javadoc/io/grpc/ServerBuilder.html#maxInboundMessageSize-int-

    The exception logged in the emulator is the following:

    [pubsub] WARNING: Exception processing message
    [pubsub] io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: gRPC message exceeds maximum size 4194304: 9000111
    [pubsub] at io.grpc.Status.asRuntimeException(Status.java:523)
    [pubsub] at io.grpc.internal.MessageDeframer.processHeader(MessageDeframer.java:387)
    [pubsub] at io.grpc.internal.MessageDeframer.deliver(MessageDeframer.java:267)
    [pubsub] at io.grpc.internal.MessageDeframer.request(MessageDeframer.java:161)
    [pubsub] at…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  9. lenguaje

    No se cambia el idioma al seleccionar Español

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  10. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  11. Subscription expiry with Cloud Functions Pub/Sub Trigger

    I've noticed an issue when a cloud function is triggered by pub/sub. When the function is deployed, a subscription is created but the expiry is set to 31 days. This means that if no messages are received for that time, the subscription disappears. After that the function appears to be deployed but will never do anything. Presumably the subscription should last as long as the function does, and be deleted if the function is removed.

    A further problem is that attempting to change the expiry time doesn't work. I tried:

    gcloud beta pubsub subscriptions update [subscription name removed] --expiration-period=never

    I…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  12. Fix princing table unit (GB -> TiB)

    Front page (https://cloud.google.com/pubsub/) pricing table says "pricing per GB", while the pricing page (https://cloud.google.com/pubsub/pricing) says "price per TiB", with both pages showing the same dollar values.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  13. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  14. Align pubsub and emulator message when topic not found

    When publishing to a topic that does not exist emulator and real pubsub return different message.
    Emulator:
    NOTFOUND: Topic not found
    Real PubSub:
    NOT
    FOUND: Resource not found

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Defect  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Cloud Pub/Sub

Categories

Feedback and Knowledge Base