Addshore added a comment.
In T214362#6028271 <https://phabricator.wikimedia.org/T214362#6028271>, @Krinkle wrote: > **Task description** > >> The constrain checks are accessible via 3 methods: >> >> - RDF action >> - Special page >> - API >> >> […] The RDF page-action exists for use by the WDQS and will not run the constraint check itself, it only exposes an RDF description of the currently stored constraints that apply to this entity. > > If I understand correctly then, the RFC action is not a way to access the result of, nor to trigger, a WDQS request. Is that right? No Part of the thing being stored may have been generated using data from a query to WDQS however. > **Task description** > >> The special page currently always re-runs the constraint checks via WDQS, it does not get or set any cache. > > Why not? Sorry, it does set the cache, bur will not get the cache. > **Task description** > >> The Query service performs checks on Wikidata entities on-demand from users. Results of these constraint checks are cached by MediaWiki (WBQC) in Memcached. […] The API only makes an internal request to WDQS if the constraint checks data is out of date, absent, or expired […]. >> […] We could make the Job […] that informs the Query service to pull the API to ingest the new data. >> >> - […] we don't currently have the result of all constraints checks for all Wikidata items stored anywhere. >> >>> ! From T201147 <https://phabricator.wikimedia.org/T201147>: >> >> At the moment constraints violations are only imported to WDQS if they are cached the moment WDQS pulls the rdfs for constraint violations for an item. There is a race condition between the WDQS poller and the constraints check execution and this is why only a fraction of constraint violations are imported. > > The above sounds contradictory to me, but I assume that must be because I'm misunderstanding something. > If I understand correctly, the authoritive source for describing items is Wikidata.org. Yes > The RDF Action on Wikidata.org exposes information relevant to constraint checks. Yes For example https://www.wikidata.org/wiki/Q64?action=constraintsrdf If this page appears blank then you'll need to hit https://www.wikidata.org/wiki/Special:ConstraintReport/Q64 first to generate and cache the results > The way we actually execute those contraint checks is by submitting a query to the Query service (WDQS), which has a nice relational model all the relationships and metadata etc. Only some checks result in queries to the WDQS. Other checks are done purely in PHP. > The thing that executes these checks is the MediaWiki WikibaseQualityConstraints extension (WBQC), and it caches the result for a day in Memcached. Yes > So far so good, I think. But then I also read that Query service (WDQS) ingests the result of these checks (which it executed itself?), and that we want the Job to notify WDQS when it is best to poll for that so that it is likely a Memcached cache-hit. > I don't know why the result of this is stored in WDQS. But, that sounds to me like you already have a place to store them all? WDQS is not really a store, for us currently it is 16 or so stores. On top of that, it isn't a store it is a query service and has all kinds of baggage attached to it because of that. Anyway, these results need to be accessible in mediawiki PHP code. WDQS instances should also not be seen as persistent or consistent. Part of the requirement of this task is that we have a copy of constraints for entities so that we can dump them and reload a WDQS instance. TASK DETAIL https://phabricator.wikimedia.org/T214362 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Addshore Cc: eprodromou, CCicalese_WMF, kchapman, Krinkle, mobrovac, abian, Lydia_Pintscher, Lucas_Werkmeister_WMDE, Marostegui, Joe, daniel, Agabi10, Aklapper, Addshore, darthmon_wmde, WDoranWMF, holger.knust, EvanProdromou, DannyS712, Nandana, kostajh, Lahi, Gq86, GoranSMilovanovic, RazeSoldier, QZanden, merbst, LawExplorer, _jensen, rosalieper, D3r1ck01, Scott_WUaS, Pchelolo, Izno, SBisson, Perhelion, Wikidata-bugs, Base, aude, GWicke, Bawolff, jayvdb, fbstj, santhosh, Jdforrester-WMF, Ladsgroup, Mbch331, Rxy, Jay8g, Ltrlg, bd808, Legoktm
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
