-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PubSub: Force push a batch of messages #9906
Labels
api: pubsub
Issues related to the Pub/Sub API.
type: question
Request for information or clarification. Not an issue.
Comments
plamut
changed the title
Force push a batch of messages
PubSub: Force push a batch of messages
Dec 2, 2019
plamut
added
api: pubsub
Issues related to the Pub/Sub API.
type: question
Request for information or clarification. Not an issue.
labels
Dec 2, 2019
Hi! Yes, it's exactly that, sorry for missing that one out when searching for similarities. Will try. Any ideas when the next release could be out? |
@hnykda No date yet, but I will propose to make it sooner rather than later. :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api: pubsub
Issues related to the Pub/Sub API.
type: question
Request for information or clarification. Not an issue.
Is your feature request related to a problem? Please describe.
Hi,
I have a simple publish for loop:
with some callback (-> I don't wait until the future is returned). The problem is that when the last batch of data is being created, the process terminates earlier than it's being sent (<MAX_LATENCY), missing some last messages.
Could there be a way of something like
publisher.join()
orpublisher.force_push()
to make sure that all messages are sent before the process terminates?Related:
The text was updated successfully, but these errors were encountered: