As a developer I want to easily understand how options are handled in streaming updater so that I can develop changes faster.
AC:
- Options are handled outside of UpdaterJob class.
As a developer I want to easily understand how options are handled in streaming updater so that I can develop changes faster.
AC:
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Extract args handling from the job objects | wikidata/query/rdf | master | +187 -156 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Gehel | T244590 [Epic] Rework the WDQS updater as an event driven application | |||
Resolved | • Zbyszko | T261119 Architecture review of Flink based WDQS Streaming Updater | |||
Resolved | • Zbyszko | T258240 Refactor Options handling in Streaming Updater |
We should do that before architecture review - so the reviewers will be able to focus on the architecture instead of understanding how unimportant things (for the architecture) work. In the future, this kind of things should be done along side standard development.
Change 626700 had a related patch set uploaded (by ZPapierski; owner: ZPapierski):
[wikidata/query/rdf@master] Extract args handling from the job objects
Change 626700 merged by jenkins-bot:
[wikidata/query/rdf@master] Extract args handling from the job objects