hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Steinbach (JIRA)" <>
Subject [jira] [Commented] (HIVE-3523) Hive info logging is broken
Date Wed, 03 Oct 2012 01:24:07 GMT


Carl Steinbach commented on HIVE-3523:

This bug is caused by HIVE-3505 which modified the file.

Before HIVE-3505 the file looked like this:



# Logging Threshold

And after HIVE-3505 it looks like this:



# Logging Threshold

One not so obvious change is that we corrected a spelling mistake, changing "log4j.thresshold"
to "log4j.threshold". The fact that log4j.threshold was previously misspelled meant that log4j
had been using the default threshold value ALL, which is equivalent to no threshold at all.
HIVE-3505 fixed the spelling mistake, which caused log4j to start using the new threshold
value WARN, which explains why INFO level messages are getting filtered out even when hive.root.logger
is set to INFO,console.

It's possible to work around this problem right now by setting both hive.log.threshold and
hive.root.logger. For example:

hive -hiveconf hive.log.threshold=INFO -hiveconf hive.root.logger=INFO,console

> Hive info logging is broken
> ---------------------------
>                 Key: HIVE-3523
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 0.10.0
>            Reporter: Shreepadma Venugopalan
>            Assignee: Carl Steinbach
> Hive Info logging is broken on trunk. hive -hiveconf hive.root.logger=INFO,console doesn't
print the output of statements to the console. 

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:

View raw message