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 B985C103F5 for ; Wed, 26 Mar 2014 17:41:31 +0000 (UTC) Received: (qmail 15201 invoked by uid 500); 26 Mar 2014 17:41:20 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 15055 invoked by uid 500); 26 Mar 2014 17:41:18 -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 14991 invoked by uid 500); 26 Mar 2014 17:41:17 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 14982 invoked by uid 99); 26 Mar 2014 17:41:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Mar 2014 17:41:16 +0000 Date: Wed, 26 Mar 2014 17:41:16 +0000 (UTC) From: "Harish Butani (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HIVE-6314) The logging (progress reporting) is too verbose 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-6314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harish Butani updated HIVE-6314: -------------------------------- Attachment: HIVE-6314.2.patch [~navis] patch didn't apply anymore; have updated it. Please check the update. > The logging (progress reporting) is too verbose > ----------------------------------------------- > > Key: HIVE-6314 > URL: https://issues.apache.org/jira/browse/HIVE-6314 > Project: Hive > Issue Type: Bug > Reporter: Sam > Assignee: Navis > Labels: logger > Attachments: HIVE-6314.1.patch.txt, HIVE-6314.2.patch > > > The progress report is issued every second even when no progress have been made: > {code} > 2014-01-27 10:35:55,209 Stage-1 map = 100%, reduce = 0%, Cumulative CPU 6.68 sec > 2014-01-27 10:35:56,678 Stage-1 map = 100%, reduce = 0%, Cumulative CPU 6.68 sec > 2014-01-27 10:35:59,344 Stage-1 map = 100%, reduce = 0%, Cumulative CPU 6.68 sec > 2014-01-27 10:36:01,268 Stage-1 map = 100%, reduce = 100%, Cumulative CPU 8.67 sec > 2014-01-27 10:36:03,149 Stage-1 map = 100%, reduce = 100%, Cumulative CPU 8.67 sec > {code} > This pollutes the logs and the screen, and people do not appreciate it as much as the designers might have thought ([http://stackoverflow.com/questions/20849289/how-do-i-limit-log-verbosity-of-hive], [http://stackoverflow.com/questions/14121543/controlling-the-level-of-verbosity-in-hive]). > It would be nice to be able to control the level of verbosity (but *not* by the {{-v}} switch!): > # Make sure that the progress report is only issued where there is something new to report; or > # Remove all the progress messages; or > # Make sure that progress is reported only every X sec (instead of every 1 second) -- This message was sent by Atlassian JIRA (v6.2#6252)