----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/7238/#review11865 -----------------------------------------------------------
trunk/common/src/java/conf/hive-log4j.properties <https://reviews.apache.org/r/7238/#comment25402> According to the log4j docs log4j.threshold defaults to the lowest possible value (i.e. ALL), which explains why this hasn't had much of impact up to this point. - Carl Steinbach 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 > >
