You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@griffin.apache.org by "Artem Shutak (JIRA)" <ji...@apache.org> on 2018/10/09 14:08:00 UTC

[jira] [Created] (GRIFFIN-205) Accuracy measure check should provide matchedFraction to store

Artem Shutak created GRIFFIN-205:
------------------------------------

             Summary: Accuracy measure check should provide matchedFraction to store
                 Key: GRIFFIN-205
                 URL: https://issues.apache.org/jira/browse/GRIFFIN-205
             Project: Griffin (Incubating)
          Issue Type: Improvement
          Components: accuracy-batch, accuracy-real-time
    Affects Versions: 1.0.0-incubating
            Reporter: Artem Shutak


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. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)