You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Phabricator (Updated) (JIRA)" <ji...@apache.org> on 2012/01/05 13:31:40 UTC

[jira] [Updated] (HIVE-2682) Clean-up logs

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

Phabricator updated HIVE-2682:
------------------------------

    Attachment: HIVE-2682.D1035.3.patch

rajat updated the revision "HIVE-2682 [jira] Clean-up logs".
Reviewers: JIRA, jsichi, jonchang, heyongqiang, njain

  Incorporated suggestions from Dymtro (dms).

REVISION DETAIL
  https://reviews.facebook.net/D1035

AFFECTED FILES
  ql/src/java/org/apache/hadoop/hive/ql/exec/GroupByOperator.java
  ql/src/java/org/apache/hadoop/hive/ql/exec/JoinOperator.java
  ql/src/java/org/apache/hadoop/hive/ql/stats/jdbc/JDBCStatsAggregator.java
  ql/src/java/org/apache/hadoop/hive/ql/stats/jdbc/JDBCStatsPublisher.java
  serde/src/java/org/apache/hadoop/hive/serde2/lazy/LazyStruct.java
  serde/src/java/org/apache/hadoop/hive/serde2/lazybinary/LazyBinaryStruct.java

                
> Clean-up logs
> -------------
>
>                 Key: HIVE-2682
>                 URL: https://issues.apache.org/jira/browse/HIVE-2682
>             Project: Hive
>          Issue Type: Wish
>          Components: Logging
>            Reporter: Rajat Goel
>            Priority: Trivial
>         Attachments: HIVE-2682.D1035.1.patch, HIVE-2682.D1035.2.patch, HIVE-2682.D1035.3.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Just wanted to cleanup some logs being printed at wrong loglevel -
> 1. org.apache.hadoop.hive.ql.exec.CommonJoinOperator prints "table 0 has 1000 rows for join key [...]" as WARNING. Is it really that? 
> 2. org.apache.hadoop.hive.ql.exec.GroupByOperator prints "Hash Table completed flushed" and "Begin Hash Table flush at close: size = 21" as WARNING. It shouldn't be.
> 3. org.apache.hadoop.hive.ql.stats.jdbc.JDBCStatsPublisher prints "Warning. Invalid statistic." which looks fishy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira