[GRIFFIN-205] Accuracy measure check should provide matchedFraction to store

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.3.1-incubating
• Component/s: accuracy-batch, accuracy-real-time
• Assignee: Artem Shutak
• Reporter: Artem Shutak
• Created: 09/Oct/18 14:07
• Updated: 29/Oct/18 15:16
• Resolved: 29/Oct/18 15:15

Description

Currently, accuracy measure results contains "total", "miss" and "matched" counts.

As a result, It's hard to analyze accuracy fraction based on results stored in ElasticSearch, because ElasticSearch does not provide straight forward capability to get "field divided by field" query results.

Accuracy measure results should also contain matchedFraction field. 

Issue Links

• links to: GitHub Pull Request #434