How to know the operation of a notification message when I subscribe redis database?
I'm using redis-py. I subscribe to redis database and read notification like this:
>>> p.psubscribe("__keyspace@__:*".format(...))
>>> for message in p.listen():
... # do something with the message
I want to get the operation of the message, like DELETE or ADD, how can I do this?
Thank you~
redis redis-py
add a comment |
I'm using redis-py. I subscribe to redis database and read notification like this:
>>> p.psubscribe("__keyspace@__:*".format(...))
>>> for message in p.listen():
... # do something with the message
I want to get the operation of the message, like DELETE or ADD, how can I do this?
Thank you~
redis redis-py
add a comment |
I'm using redis-py. I subscribe to redis database and read notification like this:
>>> p.psubscribe("__keyspace@__:*".format(...))
>>> for message in p.listen():
... # do something with the message
I want to get the operation of the message, like DELETE or ADD, how can I do this?
Thank you~
redis redis-py
I'm using redis-py. I subscribe to redis database and read notification like this:
>>> p.psubscribe("__keyspace@__:*".format(...))
>>> for message in p.listen():
... # do something with the message
I want to get the operation of the message, like DELETE or ADD, how can I do this?
Thank you~
redis redis-py
redis redis-py
asked Nov 13 '18 at 9:09
batmancnbatmancn
1389
1389
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Per the documentation (https://github.com/andymccurdy/redis-py#publish--subscribe), when calling listen()
, the message
is returned as a dictionary:
- type: One of the following: 'subscribe', 'unsubscribe', 'psubscribe', 'punsubscribe', 'message', 'pmessage'
- channel: The channel [un]subscribed to or the channel a message was published to
- pattern: The pattern that matched a published message's channel. Will be None in all cases except for 'pmessage' types.
- data: The message data. With [un]subscribe messages, this value will be the number of channels and patterns the connection is currently subscribed to. With [p]message messages, this value will be the actual published message.
In the case of the '__keyspace*' pattern, the data
key in the message
dict holds the operation's name. Put differently:
>>> p.psubscribe("__keyspace@__:*")
>>> for message in p.listen():
... print(message['data']) # print the operation
Note: the call to format(...)
appears to be not needed in your sample.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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%2f53277395%2fhow-to-know-the-operation-of-a-notification-message-when-i-subscribe-redis-datab%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Per the documentation (https://github.com/andymccurdy/redis-py#publish--subscribe), when calling listen()
, the message
is returned as a dictionary:
- type: One of the following: 'subscribe', 'unsubscribe', 'psubscribe', 'punsubscribe', 'message', 'pmessage'
- channel: The channel [un]subscribed to or the channel a message was published to
- pattern: The pattern that matched a published message's channel. Will be None in all cases except for 'pmessage' types.
- data: The message data. With [un]subscribe messages, this value will be the number of channels and patterns the connection is currently subscribed to. With [p]message messages, this value will be the actual published message.
In the case of the '__keyspace*' pattern, the data
key in the message
dict holds the operation's name. Put differently:
>>> p.psubscribe("__keyspace@__:*")
>>> for message in p.listen():
... print(message['data']) # print the operation
Note: the call to format(...)
appears to be not needed in your sample.
add a comment |
Per the documentation (https://github.com/andymccurdy/redis-py#publish--subscribe), when calling listen()
, the message
is returned as a dictionary:
- type: One of the following: 'subscribe', 'unsubscribe', 'psubscribe', 'punsubscribe', 'message', 'pmessage'
- channel: The channel [un]subscribed to or the channel a message was published to
- pattern: The pattern that matched a published message's channel. Will be None in all cases except for 'pmessage' types.
- data: The message data. With [un]subscribe messages, this value will be the number of channels and patterns the connection is currently subscribed to. With [p]message messages, this value will be the actual published message.
In the case of the '__keyspace*' pattern, the data
key in the message
dict holds the operation's name. Put differently:
>>> p.psubscribe("__keyspace@__:*")
>>> for message in p.listen():
... print(message['data']) # print the operation
Note: the call to format(...)
appears to be not needed in your sample.
add a comment |
Per the documentation (https://github.com/andymccurdy/redis-py#publish--subscribe), when calling listen()
, the message
is returned as a dictionary:
- type: One of the following: 'subscribe', 'unsubscribe', 'psubscribe', 'punsubscribe', 'message', 'pmessage'
- channel: The channel [un]subscribed to or the channel a message was published to
- pattern: The pattern that matched a published message's channel. Will be None in all cases except for 'pmessage' types.
- data: The message data. With [un]subscribe messages, this value will be the number of channels and patterns the connection is currently subscribed to. With [p]message messages, this value will be the actual published message.
In the case of the '__keyspace*' pattern, the data
key in the message
dict holds the operation's name. Put differently:
>>> p.psubscribe("__keyspace@__:*")
>>> for message in p.listen():
... print(message['data']) # print the operation
Note: the call to format(...)
appears to be not needed in your sample.
Per the documentation (https://github.com/andymccurdy/redis-py#publish--subscribe), when calling listen()
, the message
is returned as a dictionary:
- type: One of the following: 'subscribe', 'unsubscribe', 'psubscribe', 'punsubscribe', 'message', 'pmessage'
- channel: The channel [un]subscribed to or the channel a message was published to
- pattern: The pattern that matched a published message's channel. Will be None in all cases except for 'pmessage' types.
- data: The message data. With [un]subscribe messages, this value will be the number of channels and patterns the connection is currently subscribed to. With [p]message messages, this value will be the actual published message.
In the case of the '__keyspace*' pattern, the data
key in the message
dict holds the operation's name. Put differently:
>>> p.psubscribe("__keyspace@__:*")
>>> for message in p.listen():
... print(message['data']) # print the operation
Note: the call to format(...)
appears to be not needed in your sample.
answered Nov 13 '18 at 13:13
Itamar HaberItamar Haber
28.3k43760
28.3k43760
add a comment |
add a comment |
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.
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%2f53277395%2fhow-to-know-the-operation-of-a-notification-message-when-i-subscribe-redis-datab%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