[
https://issues.apache.org/jira/browse/HIVE-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184505#comment-13184505
]
Namit Jain commented on HIVE-2682:
----------------------------------
Sorry Ashutosh, didn't notice that you are looking at it.
> Clean-up logs
> -------------
>
> Key: HIVE-2682
> URL: https://issues.apache.org/jira/browse/HIVE-2682
> Project: Hive
> Issue Type: Wish
> Components: Logging
> Affects Versions: 0.8.1, 0.9.0
> Reporter: Rajat Goel
> Assignee: Rajat Goel
> Priority: Trivial
> Labels: logging
> Attachments: HIVE-2682.D1035.1.patch, HIVE-2682.D1035.2.patch,
> HIVE-2682.D1035.3.patch, hive-2682.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
