In https://phabricator.wikimedia.org/T137370#2388018, @mobrovac said:
In T137370#2385142, @Halfak wrote:
Do you have suggestions on what steps we might go through to make use of it?I think the first and foremost is to set-up a meeting where we can understand your concrete needs. All I'm understanding from this ticket is we need a pregeneration service to run query X on every edit, which is a really broad request. What kind of edits do you target? What does the outgoing request to ORES look like?
In the end, it could be that Change Propagation is not granular enough as we sync some models and not others.
It could be, but without having a proper and clear conversation about your needs, we likely won't find out ;) In general, Change Prop allows you to specify the events you want to react to and filter on individual fields, so from my little understanding of your needs, I don't think it'll be a problem accommodating them.
FYI, Change Propagation is in charge of refreshing the complete RESTBase content. We used to do this via the JobQueue, but have moved to EventBus and Change Propagation since, as it is a more stable and powerful system.
This task is done when a conversation about switching to Change Propagation is completed and, if positive, tasks are created for the next steps.