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 D1E0C18F21 for ; Thu, 21 Jan 2016 22:21:41 +0000 (UTC) Received: (qmail 84140 invoked by uid 500); 21 Jan 2016 22:21:40 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 84016 invoked by uid 500); 21 Jan 2016 22:21:40 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 83938 invoked by uid 99); 21 Jan 2016 22:21:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jan 2016 22:21:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 478742C1F71 for ; Thu, 21 Jan 2016 22:21:40 +0000 (UTC) Date: Thu, 21 Jan 2016 22:21:40 +0000 (UTC) From: "Li Lu (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4224) Support fetching entities by UID and change the REST interface to conform to current REST APIs' in YARN 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-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111491#comment-15111491 ] Li Lu commented on YARN-4224: ----------------------------- Thanks [~varun_saxena]. The latest patch generally LGTM. Some minor comments: 1. Why we're changing TimelineReaderManager#getEntities from default to public? Do we plan to make timeline reader manager to be visible to the outside world, or everyone should talk to the reader server via its WS? 2. TimelineReaderUtil, maybe we'd like to have a separate class for those parse operations? Sometimes it's not easy to find out if a method is supported in util if we mix all of those util methods inside a big util class. 3. TimelineReaderWebService#handleException, BadRequestException is a subclass of WebApplicationException so you may want to remove it from the declaration. I'd encourage everyone working on the branch to take a look at those proposed REST APIs. So far I think they are fine, but I'd like to wait a day or two and think about them for one more round. > Support fetching entities by UID and change the REST interface to conform to current REST APIs' in YARN > ------------------------------------------------------------------------------------------------------- > > Key: YARN-4224 > URL: https://issues.apache.org/jira/browse/YARN-4224 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Affects Versions: YARN-2928 > Reporter: Varun Saxena > Assignee: Varun Saxena > Labels: yarn-2928-1st-milestone > Attachments: YARN-4224-YARN-2928.01.patch, YARN-4224-feature-YARN-2928.04.patch, YARN-4224-feature-YARN-2928.05.patch, YARN-4224-feature-YARN-2928.wip.02.patch, YARN-4224-feature-YARN-2928.wip.03.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)