From yarn-issues-return-155170-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Fri Oct 12 04:22:05 2018 Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 29E39192EE for ; Fri, 12 Oct 2018 04:22:05 +0000 (UTC) Received: (qmail 32122 invoked by uid 500); 12 Oct 2018 04:22:05 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 32073 invoked by uid 500); 12 Oct 2018 04:22:04 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 32062 invoked by uid 99); 12 Oct 2018 04:22:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Oct 2018 04:22:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 5D3C81805A3 for ; Fri, 12 Oct 2018 04:22:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 4uwIsIKAOkqZ for ; Fri, 12 Oct 2018 04:22:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 5C7665F4A9 for ; Fri, 12 Oct 2018 04:22:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 63B8BE0E1D for ; Fri, 12 Oct 2018 04:22:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3EB6924DC7 for ; Fri, 12 Oct 2018 04:22:00 +0000 (UTC) Date: Fri, 12 Oct 2018 04:22:00 +0000 (UTC) From: "Rohith Sharma K S (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-8834) Provide Java client for fetching Yarn specific entities from TimelineReader MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-8834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16647415#comment-16647415 ] Rohith Sharma K S commented on YARN-8834: ----------------------------------------- bq. Do we need some documentation examples for this? This JIRA focus on YARN entities which are consumed by yarn client. So, we do not need any doc update for this now. Once we expose generic entity API's, we need to update doc. > Provide Java client for fetching Yarn specific entities from TimelineReader > --------------------------------------------------------------------------- > > Key: YARN-8834 > URL: https://issues.apache.org/jira/browse/YARN-8834 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelinereader > Reporter: Rohith Sharma K S > Assignee: Abhishek Modi > Priority: Critical > Fix For: 3.2.0, 3.0.3, 3.1.2, 3.3.0 > > Attachments: YARN-8834.001.patch, YARN-8834.002.patch, YARN-8834.003.patch, YARN-8834.004.patch, YARN-8834.005.patch, YARN-8834.006.patch > > > While reviewing YARN-8303, we felt that it is necessary to provide TimelineReaderClient which wraps all the REST calls in it so that user can just provide application or container ids along with filters.Currently fetching entities from TimelineReader is only via REST call or somebody need to write java client get entities. > It is good to provide TimelineReaderClient which fetch entities from TimelineReaderServer. This will be more useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org