hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Mackrory" <mackror...@gmail.com>
Subject Re: Review Request: HIVE-3505: Making the log4j threshold overrideable
Date Mon, 24 Sep 2012 22:31:27 GMT


> On Sept. 24, 2012, 10:23 p.m., Carl Steinbach wrote:
> > trunk/common/src/java/conf/hive-log4j.properties, line 27
> > <https://reviews.apache.org/r/7238/diff/1/?file=159530#file159530line27>
> >
> >     "threshhold" should be "threshold". I'm wondering if this spelling error is
one of the reasons this hasn't been working?

I suspect the only property that's been affecting the behavior I've been observing has been
hive.root.logger, because it acted like "WARN" before and acts like "INFO" now. After fixing
the typo in the config file on my test cluster, both the hive CLI output and the server logs
appear the same. I'll attach a patch with the typo corrected, but I'm unsure what this will
actually affect - but it probably isn't too dangerous.


- Sean


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7238/#review11863
-----------------------------------------------------------


On Sept. 24, 2012, 10:31 p.m., Sean Mackrory wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/7238/
> -----------------------------------------------------------
> 
> (Updated Sept. 24, 2012, 10:31 p.m.)
> 
> 
> Review request for hive.
> 
> 
> Description
> -------
> 
> I describe the motivation for this change in the bug.
> 
> 
> This addresses bug HIVE-3505.
>     https://issues.apache.org/jira/browse/HIVE-3505
> 
> 
> Diffs
> -----
> 
>   trunk/common/src/java/conf/hive-log4j.properties 1389562 
> 
> Diff: https://reviews.apache.org/r/7238/diff/
> 
> 
> Testing
> -------
> 
> Used Hive on a pseudo-distributed Hadoop installation. Was able to override the log4j
threshold and enable audit-logging when starting a service by invoking with -Dhive.log.threshold=INFO.
> 
> 
> Thanks,
> 
> Sean Mackrory
> 
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message