You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@griffin.apache.org by "Dmitry Ershov (JIRA)" <ji...@apache.org> on 2019/02/20 14:26:00 UTC
[jira] [Created] (GRIFFIN-233) ElasticSearchSink modification
Dmitry Ershov created GRIFFIN-233:
-------------------------------------
Summary: ElasticSearchSink modification
Key: GRIFFIN-233
URL: https://issues.apache.org/jira/browse/GRIFFIN-233
Project: Griffin (Incubating)
Issue Type: Improvement
Reporter: Dmitry Ershov
Actually ElasticSearchSink does not save the information about yarn applicationId. As a first step we propose to add this applicationId into measure results. The part of response will be looking like that:
{noformat}
"_source": {
"name": "de_demo_results_comparision",
"tmst": 1548937782703,
"value": {
"total": 74,
"miss": 74,
"matched": 0,
"matchedFraction": 0
},
"applicationId": "application_1548923518014_0001"
}{noformat}
In the next steps we can implement API, that could find a specific metric information basing on certain applicationId. In this way we could include our griffin jobs in various ETL processes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)