EDIT: after a longer discussion below, we decided to add a new stream of events recording changes to the logging table. These would be very useful to us and to the collection of events in general. We will also add log id to the other events mentioned below. The strategy is basically to do both of these things and use whatever makes it out to production first.
Who: I'll be implementing this as part of our work on incremental updates.
What: We need a solid link between EventBus events and what we get out of the mysql databases. For revisions, this is rev_id, but for page and user events, we think log_id is great, maybe log_timestamp too if it's free.
When: I'm going to get started soon, hopefully we can wrap up reviews over the next couple of months.
Asks: I'd love some help with reviews and pointers if I get lost. Here are the events we need log entries for:
event | note |
page deleted | Available! and according to this has id and timestamp? |
page restored | no logEntry available yet |
page moved | no logEntry available yet |
page create | we have a rev_id for this so it's ok |
user {create, rename} | events not yet available, see T262205 and add log info to the schema |
user alterblocks | no logEntry available yet |