hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-5577) [Atsv2] Publish parent/child entities value as string rather than value as object.
Date Mon, 29 Aug 2016 11:47:20 GMT

     [ https://issues.apache.org/jira/browse/YARN-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rohith Sharma K S updated YARN-5577:
------------------------------------
    Attachment: YARN-5577.patch

Updated the documentation patch  for passing an object in infofilters along with an example.

> [Atsv2] Publish parent/child entities value as string rather than value as object.
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-5577
>                 URL: https://issues.apache.org/jira/browse/YARN-5577
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: timelinereader, timelineserver
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>         Attachments: YARN-5577.patch
>
>
> In HierarchicalTimelineEntity, setparent/addChild allows to set parent/child entities
at INFO level. The key is an string and value as an object. 
> Like below, for YARN_CONTAINER entity parent entity set for application.
> {code}
> "SYSTEM_INFO_PARENT_ENTITY": {
>        "type": "YARN_APPLICATION",
>        "id": "application_1471931266232_0024"
>      }
> {code}
> But to use infofilter on entity type YARN_CONTAINER for an specific applicationId, IIUC
there is no way to pass object as value in infofilter. 
> To make easier retrieval either
> # publish parent/child entity id and type as string rather that object like below
> {code}
> "SYSTEM_INFO_PARENT_ENTITY_TYPE": "YARN_APPLICATION"
> "SYSTEM_INFO_PARENT_ENTITY_ID":"application_1471931266232_0024"
> {code}
> OR
> # Add ability to provide object as filter with below format like {{infofilters=SYSTEM_INFO_PARENT_ENTITY
eq ((type eq YARN_APPLICATION) AND (id eq application_1471931266232_0024))}}
> I believe 2nd approach will be well applicable for any entities. But I am not sure does
HBase supports such a custom filters while scanning a table. 
> 1st approaches will be much easier to change. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message