You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/01/09 11:31:19 UTC

[jira] [Commented] (HIVE-3230) Make logging of plan progress in HadoopJobExecHelper configurable

    [ https://issues.apache.org/jira/browse/HIVE-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548264#comment-13548264 ] 

Hudson commented on HIVE-3230:
------------------------------

Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
    HIVE-3230 Make logging of plan progress in HadoopJobExecHelper configurable
(Kevin Wilfong via namit) (Revision 1362782)

     Result = ABORTED
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1362782
Files : 
* /hive/trunk/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java
* /hive/trunk/conf/hive-default.xml.template
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/HadoopJobExecHelper.java

                
> Make logging of plan progress in HadoopJobExecHelper configurable
> -----------------------------------------------------------------
>
>                 Key: HIVE-3230
>                 URL: https://issues.apache.org/jira/browse/HIVE-3230
>             Project: Hive
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 0.10.0
>            Reporter: Kevin Wilfong
>            Assignee: Kevin Wilfong
>            Priority: Minor
>             Fix For: 0.10.0
>
>         Attachments: HIVE-3230.1.patch.txt, HIVE-3230.2.patch.txt, HIVE-3230.3.patch.txt, HIVE-3230.4.patch.txt
>
>
> Currently, by default, every second a job is run a massive JSON string containing the query plan, the tasks, and some counters is logged to the hive_job_log.  For large, long running jobs that can easily reach gigabytes of data. This logging should be configurable as average user doesn't need this logging.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira