MZMcBride added a subscriber: MZMcBride.
TASK DETAIL
https://phabricator.wikimedia.org/T84923
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
bd808 added a subscriber: bd808.
bd808 added a comment.
can support large delays (order of days) for individual consumers
Do you have a strong use case to support this need? Kafka may very well be able
to support this but I'm wondering it there is a specific and strong reason for
such a long
Krenair added a subscriber: Krenair.
TASK DETAIL
https://phabricator.wikimedia.org/T84923
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To:
JanZerebecki added a subscriber: daniel.
JanZerebecki added a comment.
While talking to @daniel he noticed that I missed that the actual serialized
diff is saved in https://www.mediawiki.org/wiki/Wikibase/Schema/wb_changes
there is just no API.
TASK DETAIL
Hardikj added a subscriber: Hardikj.
TASK DETAIL
https://phabricator.wikimedia.org/T84923
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To:
yuvipanda added subscribers: Halfak, yuvipanda.
TASK DETAIL
https://phabricator.wikimedia.org/T84923
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
EMAIL PREFERENCES
mobrovac added a subscriber: mobrovac.
TASK DETAIL
https://phabricator.wikimedia.org/T84923
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
username.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
JanZerebecki added a subscriber: JanZerebecki.
JanZerebecki added a comment.
The nature of these event type candidates is such that they are changes with a
log existing at the provider. The only persistent state that each consuming
service needs to know is the revision/time up to which it has