Smalyshev added a comment.
See: https://www.mediawiki.org/wiki/Wikibase/Indexing/RDF_Dump_Format#Constraints (currently enabled only for internal cluster, soon on public one too).TASK DETAILhttps://phabricator.wikimedia.org/T172380EMAIL
Jonas added a comment.
Yes, according to last weeks stats execution time of each individual(!) check can take up to 8 seconds.
I am afraid we can not run checks within a query.
The feature itself sounds very useful to me!
Maybe we can store the results of checks that were executed somewhere, so
Lucas_Werkmeister_WMDE added a comment.
@Smalyshev I don’t think the lack of grouping support in MWAPI is a big problem here – constraint checks are just expensive at the moment, so I expect such queries would take a long time regardless of whether the actual API requests are grouped or not.TASK
Smalyshev added a comment.
If there is a Mediawiki API that checks constraints, that would be the best way to integrate - we just add it to supported APIs and use it. Note however MWAPI gate right now can not group queries, i.e. if it is used with results of other patters, it would do query per
MisterSynergy added a comment.
I thought of a new SERVICE as well, but I actually do not really have a preference how this should be implemented. Devs will find the best solution, I guess…TASK DETAILhttps://phabricator.wikimedia.org/T172380EMAIL
Esc3300 added a comment.
oh .. forget what I just wrote.
Maybe a new service for WQS would be easiest solution.TASK DETAILhttps://phabricator.wikimedia.org/T172380EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Esc3300Cc: Esc3300, Aklapper, PokestarFan,
Esc3300 added a comment.
I inserted numbering in the task description.
I think (4.) could be done easily with the SPARQL query links on property talk pages.
Maybe (2.) and (3.) could be done by some combination .. but it's likely to time out.
On the other hand, if you start from a list of
