Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 23 Nov 2016 01:54:58 +0000 (UTC)
From: "Prasanth Jayachandran (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.13020986.1479257137000.345696.1479866098723@Atlassian.JIRA>
In-Reply-To: <JIRA.13020986.1479257137000@Atlassian.JIRA>
References: <JIRA.13020986.1479257137000@Atlassian.JIRA> <JIRA.13020986.1479257137591@arcas>
Subject: [jira] [Issue Comment Deleted] (HIVE-15217) Add watch mode to llap
 status tool
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 23 Nov 2016 01:55:00 -0000


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

Prasanth Jayachandran updated HIVE-15217:
-----------------------------------------
    Comment: was deleted

(was: Addressed [~gopalv]'s review comments. Added a unit test case to verify the same but was hit by kryo issue. Will look at it later. 
Having 2 kryo factories one for serialization and other for cloning will also work because of this kryo bug. The easier fix is to leave the Statistics object non-transient as such. This will however add to the serialized size of the plan which shouldn't be big. )

> Add watch mode to llap status tool
> ----------------------------------
>
>                 Key: HIVE-15217
>                 URL: https://issues.apache.org/jira/browse/HIVE-15217
>             Project: Hive
>          Issue Type: Improvement
>          Components: llap
>    Affects Versions: 2.2.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>            Priority: Minor
>         Attachments: HIVE-15217.1.patch
>
>
> There is few seconds overhead for launching the llap status command. To avoid we can add "watch" mode to llap status tool that refreshes the status after configured interval. 


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