[
https://issues.apache.org/jira/browse/GRIFFIN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604152#comment-16604152
]
Lionel Liu commented on GRIFFIN-102:
------------------------------------
Actually it's not that easy.
Say we have a metric named "test" with some points between 2018-08-09T12:00 and
2018-08-10T12:00, and the metric is deleted. After 3 days, we create another
metric also named "test", and there will be metric points after
2018-08-13T12:00. In ES, we only saved the metric name "test" as the key, when
we fetch the metrics of "test", ES will return two slices of data. If the two
metrics are in the same type like "accuracy", it will confuse the latter user.
If they are in different types, it will lead error.
> [Service] Fix bug of fetching metrics of different jobs with the same name
> --------------------------------------------------------------------------
>
> Key: GRIFFIN-102
> URL: https://issues.apache.org/jira/browse/GRIFFIN-102
> Project: Griffin (Incubating)
> Issue Type: Bug
> Reporter: Lionel Liu
> Assignee: He Wang
> Priority: Major
> Labels: SP_5
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> When fetch metrics from ES, if one job has the same name with another job
> which was deleted, the metrics would be union and confuse.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
