dcausse added a comment.
@Joe the main reason for me is that we need to do state-full computation over multiple event streams: - we want to union multiple event streams - we want to reorder events - we want to keep a state (last seen rev per entity) ChangeProp is a "mostly" stateless service (except for deduplication) and has not been designed (I think) as a framework you can build on top, adding new actions seems trivial but this is not exactly what we need. Adapting ChangeProp to do windowing functions, combining streams, keeping a state that is consistent with kafka offsets seemed a bit complex to write from scratch in ChangeProp. What flink provides is exactly that: a framework where you can build state-full apps and where event time semantic is at the core of its design (concept of watermarks). Also I don't see flink as doing the same type of work than change prop, change prop being a configurable service to schedule actions based on events, flink is more a framework to do stream processing. TASK DETAIL https://phabricator.wikimedia.org/T247058 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: dcausse Cc: Joe, Aklapper, dcausse, Zbyszko, Gehel, darthmon_wmde, Legado_Shulgin, Nandana, Davinaclare77, Qtn1293, Techguru.pc, Lahi, Gq86, Lucas_Werkmeister_WMDE, GoranSMilovanovic, Th3d3v1ls, Hfbn0, QZanden, EBjune, merbst, LawExplorer, Zppix, _jensen, rosalieper, Scott_WUaS, Jonas, Xmlizer, Wong128hk, jkroll, Smalyshev, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, faidon, Mbch331, Rxy, Jay8g, fgiunchedi
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
