Go pubsub message handling, separate function
up vote
0
down vote
favorite
I'm trying to fetch messages from pubsub, but I'm kind of lost now. I want to separate the message handler from the actual "fetcher". So basically I want to do this:
sub := pubsubClient.Subscription("bla")
err := sub.Receive(context.Background(), handleMessage)
func handleMessage(ctx context.Context, msg *pubsub.Message) {
fmt.Println(msg)
}
Unfortunately this does not work. I'm getting the following error: Cannot use handleMessage (type func(ctx context.Context, msg *pubsub.Message) error as type func(context.Context, *Message)
.
I can solve this by doing this:
err := sub.Receive(context.Background(), func(ctx context.Context, msg *pubsub.Message) {
if err := handleMessage(msg); err != nil { // individual message processing went wrong
msg.Nack()
return
}
msg.Ack()
})
But I prefer to separate the actual handler function. Any help is appreciated.
go google-cloud-pubsub
add a comment |
up vote
0
down vote
favorite
I'm trying to fetch messages from pubsub, but I'm kind of lost now. I want to separate the message handler from the actual "fetcher". So basically I want to do this:
sub := pubsubClient.Subscription("bla")
err := sub.Receive(context.Background(), handleMessage)
func handleMessage(ctx context.Context, msg *pubsub.Message) {
fmt.Println(msg)
}
Unfortunately this does not work. I'm getting the following error: Cannot use handleMessage (type func(ctx context.Context, msg *pubsub.Message) error as type func(context.Context, *Message)
.
I can solve this by doing this:
err := sub.Receive(context.Background(), func(ctx context.Context, msg *pubsub.Message) {
if err := handleMessage(msg); err != nil { // individual message processing went wrong
msg.Nack()
return
}
msg.Ack()
})
But I prefer to separate the actual handler function. Any help is appreciated.
go google-cloud-pubsub
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to fetch messages from pubsub, but I'm kind of lost now. I want to separate the message handler from the actual "fetcher". So basically I want to do this:
sub := pubsubClient.Subscription("bla")
err := sub.Receive(context.Background(), handleMessage)
func handleMessage(ctx context.Context, msg *pubsub.Message) {
fmt.Println(msg)
}
Unfortunately this does not work. I'm getting the following error: Cannot use handleMessage (type func(ctx context.Context, msg *pubsub.Message) error as type func(context.Context, *Message)
.
I can solve this by doing this:
err := sub.Receive(context.Background(), func(ctx context.Context, msg *pubsub.Message) {
if err := handleMessage(msg); err != nil { // individual message processing went wrong
msg.Nack()
return
}
msg.Ack()
})
But I prefer to separate the actual handler function. Any help is appreciated.
go google-cloud-pubsub
I'm trying to fetch messages from pubsub, but I'm kind of lost now. I want to separate the message handler from the actual "fetcher". So basically I want to do this:
sub := pubsubClient.Subscription("bla")
err := sub.Receive(context.Background(), handleMessage)
func handleMessage(ctx context.Context, msg *pubsub.Message) {
fmt.Println(msg)
}
Unfortunately this does not work. I'm getting the following error: Cannot use handleMessage (type func(ctx context.Context, msg *pubsub.Message) error as type func(context.Context, *Message)
.
I can solve this by doing this:
err := sub.Receive(context.Background(), func(ctx context.Context, msg *pubsub.Message) {
if err := handleMessage(msg); err != nil { // individual message processing went wrong
msg.Nack()
return
}
msg.Ack()
})
But I prefer to separate the actual handler function. Any help is appreciated.
go google-cloud-pubsub
go google-cloud-pubsub
asked Nov 22 at 8:31
Rogier Lommers
8112820
8112820
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53426730%2fgo-pubsub-message-handling-separate-function%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown