Addshore added a subscriber: Lydia_Pintscher. Addshore added a comment.
In T214362#4980932 <https://phabricator.wikimedia.org/T214362#4980932>, @Lucas_Werkmeister_WMDE wrote: > > and once we have data for all items persistently stored in theory the user would never ask for an items constraint check and it not be there (thus no writing to the storage on request) > > > > > Once the storage is fully populated this isn't even a case we need to think about. > > I don’t think these are true – I think it will still be possible that we realize after retrieving the cached result that it is stale, because some referenced page has been edited in the meantime, or because a certain point in time has passed. That is a good point. We could consider having different API behaviour for the GET vs POST, POST being the only one that would get fresh results. We could also do a variety of other things, for example: - re run the constraint checks in the web request and then present them to the user - send an error to the client saying they are outdated and to retry later while running the checks in the job queue - serve the outdated results but trigger a job to update the stored results? Perhaps we need to figure out exactly how we want this to appear to the user @Lydia_Pintscher so that we can figure out what we want to do in the background. TASK DETAIL https://phabricator.wikimedia.org/T214362 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Addshore Cc: Lydia_Pintscher, Lucas_Werkmeister_WMDE, Marostegui, Joe, daniel, Agabi10, Aklapper, Addshore, Nandana, kostajh, Lahi, Gq86, GoranSMilovanovic, QZanden, merbst, LawExplorer, _jensen, D3r1ck01, SBisson, Eevans, mobrovac, Hardikj, Wikidata-bugs, aude, GWicke, jayvdb, fbstj, santhosh, Jdforrester-WMF, Mbch331, Rxy, Jay8g, Ltrlg, bd808, Legoktm
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
