HBaseClient.java may use external log4j.properties file
The executor/HbaseClient.java class unconditionally configures
log4j using conf/log4j.hdfs.config file. This caused a problem
for external clients in that their log4j configurations were reset
causing all subsequent client events to be written to the
HBaseClient log file. A client may want its log events written
to its own log file or console. This commit introduces a new property
"hbaseclient.log4j.properties" so clients can specify which log4j
properties file to use when HBaseClient sets up logging. For internal
clients such as sqlci the existing behavior is maintained.
Reviewed: https:/ /review. trafodion. org/1148 /github. com/trafodion/ core/commit/ daf701a264c79d3 5a889e9bac7d5ef a583b081dd
Committed: https:/
Submitter: Trafodion Jenkins
Branch: master
commit daf701a264c79d3 5a889e9bac7d5ef a583b081dd
Author: matbrown <email address hidden>
Date: Tue Feb 17 18:57:01 2015 +0000
HBaseClient .java may use external log4j.properties file
The executor/ HbaseClient. java class unconditionally configures hdfs.config file. This caused a problem t.log4j. properties" so clients can specify which log4j
log4j using conf/log4j.
for external clients in that their log4j configurations were reset
causing all subsequent client events to be written to the
HBaseClient log file. A client may want its log events written
to its own log file or console. This commit introduces a new property
"hbaseclien
properties file to use when HBaseClient sets up logging. For internal
clients such as sqlci the existing behavior is maintained.
Change-Id: Ic60b5d7f0e03a3 08f057ee6a9a9fe aa47c4aaf1c
Closes-Bug: #1419112