You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Prasanth Jayachandran (JIRA)" <ji...@apache.org> on 2016/08/24 22:01:20 UTC

[jira] [Commented] (HIVE-14625) Minor qtest fixes

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

Prasanth Jayachandran commented on HIVE-14625:
----------------------------------------------

Setting PerfLogger to INFO will cause failures for operation logging tests.
https://github.com/apache/hive/blob/master/itests/hive-unit/src/test/java/org/apache/hive/service/cli/operation/TestOperationLoggingAPIWithMr.java

Why do we want to change perf logger level to INFO? I don't think that will contribute to huge percent of logging. I have seen log lines from blockreaders that are most common than perflogger. I think we should set log level for hive package to be DEBUG and all others at INFO level. 

Also, junit to RunListener that we can implement for log,computing time etc. I guess that will more cleaner?

> Minor qtest fixes
> -----------------
>
>                 Key: HIVE-14625
>                 URL: https://issues.apache.org/jira/browse/HIVE-14625
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: HIVE-14625.01.patch
>
>
> Log times for CoreCliDriver
> Exit early if cleanup and createsSources fails
> Turn PerfLogger off for ptests



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