Page MenuHomePhabricator

Add uniqueness constraints to ores_classification
Closed, ResolvedPublic


For each revision+model+class, there should only be one score, and for each revision+model only one class should be the predicted one.

Event Timeline

Catrope created this task.Aug 26 2016, 12:44 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 26 2016, 12:44 AM

Change 306854 had a related patch set uploaded (by Catrope):
Add UNIQUE indexes to ores_classification

Halfak added a subscriber: Halfak.

@Catrope, do you want to assign this task to yourself since you started work?

Change 306854 merged by jenkins-bot:
Add UNIQUE indexes to ores_classification

Ladsgroup added a subscriber: Ladsgroup.

Okay. It was only bad data in the beta cluster. We are okay to deploy this change

Halfak closed this task as Resolved.Sep 14 2016, 12:57 AM
Halfak claimed this task.