Nuria added a comment. > EventLogging: Decode, validate and enqueue JSON events for EL.
mmm..I am not sure who would be the users of this endpoint at this time, do you have a case for EL that is not served by varnish endpoint? > Provide edit related events (ex: edit, creation, deletion, revision deletion, > rename). This is a strong use case and analytics cares a lot about this data. Now, the priority here is the data and I am not sure this data would be published to kafka via rest endpoint given that the monolog integration with mediawiki is already set up. I am not trying to get in the way but rather truly trying to understand here why the edit stream use case implies a rest endpoint. Seems to me (and I defer to @ottomata on this point) that in order to deliver value the critical path includes: some schema registry system plus publishing of edit stream directly into kafka. As @joe pointed out separation of systems can be achieved by abstracting interface and implementation. TASK DETAIL https://phabricator.wikimedia.org/T114443 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Nuria Cc: EBernhardson, bd808, Joe, dr0ptp4kt, madhuvishy, Nuria, ori, faidon, aaron, GWicke, mobrovac, Halfak, Eevans, Ottomata, Matanya, Aklapper, JAllemandou, jkroll, Smalyshev, Hardikj, Wikidata-bugs, Jdouglas, RobH, aude, Deskana, Manybubbles, mark, JanZerebecki, RobLa-WMF, fgiunchedi, Dzahn, jeremyb, chasemp, Krenair _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
