gerritbot added a comment.
Change 449329 merged by jenkins-bot:
[mediawiki/extensions/Wikibase@master] Add documentation for wikibase:hasViolationForConstraint
https://gerrit.wikimedia.org/r/449329TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL
Lydia_Pintscher added a comment.
Awesome! Can we get a more detailed description for the queries in the description so Léa can announce it?TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Smalyshev,
gerritbot added a comment.
Change 447742 merged by Gehel:
[operations/puppet@production] Enable constraints loading everywhere
https://gerrit.wikimedia.org/r/447742TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL
gerritbot added a comment.
Change 449329 had a related patch set uploaded (by Smalyshev; owner: Smalyshev):
[mediawiki/extensions/Wikibase@master] Add documentation for wikibase:hasViolationForConstraint
https://gerrit.wikimedia.org/r/449329TASK
gerritbot added a comment.
Change 447741 merged by Gehel:
[operations/puppet@production] Enable constraints fetching on internal cluster
https://gerrit.wikimedia.org/r/447741TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL
gerritbot added a comment.
Change 447740 merged by Gehel:
[operations/puppet@production] Enable constraints fetching for test cluster
https://gerrit.wikimedia.org/r/447740TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL
gerritbot added a comment.
Change 447742 had a related patch set uploaded (by Smalyshev; owner: Smalyshev):
[operations/puppet@production] Enable constraints loading everywhere
https://gerrit.wikimedia.org/r/447742TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL
gerritbot added a comment.
Change 447740 had a related patch set uploaded (by Smalyshev; owner: Smalyshev):
[operations/puppet@production] Enable constraints fetching for test cluster
https://gerrit.wikimedia.org/r/447740TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL
gerritbot added a comment.
Change 447741 had a related patch set uploaded (by Smalyshev; owner: Smalyshev):
[operations/puppet@production] Enable constraints fetching on internal cluster
https://gerrit.wikimedia.org/r/447741TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL
gerritbot added a comment.
Change 445454 merged by Gehel:
[operations/puppet@production] Enable fetching constraints for Updater
https://gerrit.wikimedia.org/r/445454TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL
gerritbot added a comment.
Change 445454 had a related patch set uploaded (by Smalyshev; owner: Smalyshev):
[operations/puppet@production] Enable fetching constraints for Updater
https://gerrit.wikimedia.org/r/445454TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL
gerritbot added a comment.
Change 434015 merged by jenkins-bot:
[wikidata/query/rdf@master] Add loading constraints data
https://gerrit.wikimedia.org/r/434015TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:
gerritbot added a comment.
Change 434015 had a related patch set uploaded (by Smalyshev; owner: Smalyshev):
[wikidata/query/rdf@master] [WIP] [DNM] Add loading constraints data
https://gerrit.wikimedia.org/r/434015TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL
Smalyshev added a comment.
Ah, it's wikimania hackathon tag, sorry, ignore that.TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: SmalyshevCc: Multichill, hoo, abian, Micru, Agabi10, Lucas_Werkmeister_WMDE,
Smalyshev added a comment.
@Lucas_Werkmeister_WMDE why did you drop the hackathon tag? Is there any problem with working on this on Hackathon?TASK DETAILhttps://phabricator.wikimedia.org/T192567EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: SmalyshevCc:
Smalyshev added a comment.
The updater usually doesn’t take more than a few seconds to reach an item, right?
Yes.
I’m skeptical whether this will be possible…
Then we need a different model.
Also, the updater needs to learn how to remove the old constraints data.
That's not a problem, we do
Lucas_Werkmeister_WMDE added a comment.
This means it will only be updated … if the constraint check can prepare the cached data by the time Updater gets to it.
The updater usually doesn’t take more than a few seconds to reach an item, right? I’m skeptical whether this will be possible…
Also,
Smalyshev added a comment.
After discussion with @Jonas here's what we can do now without very major efforts:
We make wbcheckconstraints API to produce RDF representation (also TBD) of the checks
We create a parameter for wbcheckconstraints to only deliver results if they can be delivered fast
Jonas added a comment.
In T192567#4157979, @Agabi10 wrote:
That would be only true for the entities that have been visited by logged in users since the deletion. It could take weeks or even months to have the required entities in the cache to be able to find and fix all the constraint violations
Agabi10 added a comment.
In T192567#4157289, @Jonas wrote:
It is ok if they are deleted. They will be repopulated over time when users execute constraint checks.
That would be only true for the entities that have been visited by logged in users since the deletion. It could take weeks or even
Jonas added a comment.
In T192567#4151226, @Smalyshev wrote:
So, constraint checks are bound to existing items? I wonder if it would be possible to expose them in the same way page properties are exposed.
Yes, kinda. The problem is they are very expensive and it can take multiple seconds or
Smalyshev added a comment.
When a constraint check is executed for an Item the result will be stored and the old result for that Item will be deleted.
So, constraint checks are bound to existing items? I wonder if it would be possible to expose them in the same way page properties are exposed.
Jonas added a comment.
In T192567#4146952, @Smalyshev wrote:
So, if you want to put a dataset into the database, here's the questions to answer:
What kind of queries we are planning to run? Which use cases they would support? I am not sure I am clear on use case for "constraint violations for
Smalyshev added a comment.
So, if you want to put a dataset into the database, here's the questions to answer:
What kind of queries we are planning to run? Which use cases they would support? I am not sure I am clear on use case for "constraint violations for actors that live in Germany and are
Lucas_Werkmeister_WMDE added a comment.
The data model for a constraint violation would be a single triple pointing from the violating statement to the constraint it violates.
A few notes on load / scale: last week (2018-04-12 – 2018-04-19), there were some 121.3K requests to the
Gehel added a comment.
A few notes (without much thinking, so don't read too much into them):
WDQS nodes are operated in a "share nothing" mode. Which means that each node is responsible to pull it's data from different places (wikidata, categories dumps, ...). This total independence between
26 matches
Mail list logo
