----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72104/#review219554 -----------------------------------------------------------
Ship it! Ship It! - Bolke de Bruin On Feb. 10, 2020, 11:22 a.m., Mariusz Górski wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/72104/ > ----------------------------------------------------------- > > (Updated Feb. 10, 2020, 11:22 a.m.) > > > Review request for atlas and Bolke de Bruin. > > > Repository: atlas > > > Description > ------- > > This patch enables logging to STDOUT from processes spawned through > atlas_start.py or atlas_config.py scripts. For now, even if configured in > log4j, logging to STDOUT was supressed (by redirecting to log files only). > > > Diffs > ----- > > distro/src/bin/atlas_config.py f09026ff9 > distro/src/bin/atlas_start.py 963faf402 > > > Diff: https://reviews.apache.org/r/72104/diff/1/ > > > Testing > ------- > > The tests were concluded by: > > 1. Building & running Atlas locally with default log4j configuration and > ENABLE_LOGGING_TO_CONSOLE variable set to true. > 2. Building & running Atlas on Openshift with log4j configuration pushing > everything to STDOUT and ENABLE_LOGGING_TO_CONSOLE variable set to true. > > In both scenarios logs were available both in the .out/.err files in the > Atlas logdir (backwards compatibility), but at the same time I was able to > see them in STDOUT of both running process (local installation) and pod > (openshift deployment). > > > Thanks, > > Mariusz Górski > >
