Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CDD6E11E1D for ; Mon, 15 Sep 2014 03:13:34 +0000 (UTC) Received: (qmail 6734 invoked by uid 500); 15 Sep 2014 03:13:34 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 6661 invoked by uid 500); 15 Sep 2014 03:13:34 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 6649 invoked by uid 500); 15 Sep 2014 03:13:34 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 6646 invoked by uid 99); 15 Sep 2014 03:13:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Sep 2014 03:13:34 +0000 Date: Mon, 15 Sep 2014 03:13:34 +0000 (UTC) From: "Dong Chen (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-7615) Beeline should have an option for user to see the query progress 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/HIVE-7615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133519#comment-14133519 ] Dong Chen commented on HIVE-7615: --------------------------------- Hi Brock, Thanks for your suggestion, and I think using the properties for filtering would work. But I still have a little concern about dealing with possible changes in the future. Two files are attached for your reference. The "complete_logs" is copied from Beeline console when it executes a query. The log has already excluded logging of the GetLog request themselves. It mainly includes logging of performance, parser, semantic analyzer, driver, and ql.exec.Task. The "simple_logs" is a subset of the complete logs and focus on job running progress. This is produced in HS2 terminal. If the complete logs is ok for users, that's fine. If we want to filter this log to simple content, since the log is generated by HS2, its format may vary based on log4j pattern HS2 using dynamically and its content may vary when new log is added during Hive development, I am afraid some fixed values might not be enough and the filtering should be more generic. What do you think? Best Regards, Dong > Beeline should have an option for user to see the query progress > ---------------------------------------------------------------- > > Key: HIVE-7615 > URL: https://issues.apache.org/jira/browse/HIVE-7615 > Project: Hive > Issue Type: Improvement > Components: CLI > Reporter: Dong Chen > Assignee: Dong Chen > Attachments: HIVE-7615.patch > > > When executing query in Beeline, user should have a option to see the progress through the outputs. > Beeline could use the API introduced in HIVE-4629 to get and display the logs to the client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)