[Wikidata-bugs] [Maniphest] [Updated] T204024: Store WikibaseQualityConstraint check data in an SQL table instead of in the cache

2018-10-31 Thread Addshore
Addshore added a project: Operations. TASK DETAILhttps://phabricator.wikimedia.org/T204024EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: AddshoreCc: Lydia_Pintscher, Pintoch, Tpt, Smalyshev, Eevans, daniel, mobrovac, Jonas, Lucas_Werkmeister_WMDE, Aklapper, A

[Wikidata-bugs] [Maniphest] [Updated] T204024: Store WikibaseQualityConstraint check data in an SQl table instead of in the cache

2018-09-11 Thread Addshore
Addshore added projects: Wikibase-Quality-Constraints, Wikidata-Campsite, wikidata-tech-focus. TASK DETAILhttps://phabricator.wikimedia.org/T204024EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: AddshoreCc: Aklapper, Addshore, Lahi, Gq86, Lucas_Werkmeister_WMD

[Wikidata-bugs] [Maniphest] [Updated] T204024: Store WikibaseQualityConstraint check data in an SQl table instead of in the cache

2018-09-11 Thread Addshore
Addshore added a parent task: T192565: Find constraint violations. TASK DETAILhttps://phabricator.wikimedia.org/T204024EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: AddshoreCc: Aklapper, Addshore, Lahi, Gq86, Lucas_Werkmeister_WMDE, GoranSMilovanovic, QZande

[Wikidata-bugs] [Maniphest] [Updated] T204024: Store WikibaseQualityConstraint check data in an SQL table instead of in the cache

2018-09-11 Thread Lucas_Werkmeister_WMDE
Lucas_Werkmeister_WMDE added a comment. Some previous discussion of this, including suggested database schemas, can be found in the comments of T179849: Cache all constraint check results per-entity.TASK DETAILhttps://phabricator.wikimedia.org/T204024EMAIL PREFERENCEShttps://phabricator.wikimedia.o

[Wikidata-bugs] [Maniphest] [Updated] T204024: Store WikibaseQualityConstraint check data in an SQL table instead of in the cache

2018-09-12 Thread mobrovac
mobrovac added projects: Services (designing), Cassandra.mobrovac added a comment. Could you describe the exact data that would be stored and its data model? I looked at T179849, but I see two different things there: in T179849#3770891 a resulting JSON blob is mentioned, but T179849#3778358 outline

[Wikidata-bugs] [Maniphest] [Updated] T204024: Store WikibaseQualityConstraint check data in an SQL table instead of in the cache

2018-09-12 Thread Addshore
Addshore added a subscriber: Smalyshev.Addshore added a comment. In T204024#4577066, @Eevans wrote: An opaque k/v store won't allow anything but discrete lookup by entity ID, how are violations queried? In other words, this seems to only be a small part of the larger model, what does that look li

[Wikidata-bugs] [Maniphest] [Updated] T204024: Store WikibaseQualityConstraint check data in an SQL table instead of in the cache

2018-09-19 Thread Pintoch
Pintoch added a comment. @Lydia_Pintscher yes indeed! For instance the aggregation at batch-level would probably not be meaningful for inverse constraints (unless there is a way to detect all the violations added and solved by an edit, not just on the item where the edit was made). But isn't this a

[Wikidata-bugs] [Maniphest] [Updated] T204024: Store WikibaseQualityConstraint check data in an SQL table instead of in the cache

2018-10-15 Thread mobrovac
mobrovac added a project: Core Platform Team Backlog (Designing). TASK DETAILhttps://phabricator.wikimedia.org/T204024EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: mobrovacCc: Lydia_Pintscher, Pintoch, Tpt, Smalyshev, Eevans, daniel, mobrovac, Jonas, Lucas_W