You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Mariusz Górski (Jira)" <ji...@apache.org> on 2019/12/11 09:37:00 UTC

[jira] [Updated] (ATLAS-3557) Configurable STDOUT/STDERR Redirect in Python entrypoint scripts

     [ https://issues.apache.org/jira/browse/ATLAS-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mariusz Górski updated ATLAS-3557:
----------------------------------
    Summary: Configurable STDOUT/STDERR Redirect in Python entrypoint scripts  (was: Configurable STDOUT Redirect in Python entrypoint scripts)

> Configurable STDOUT/STDERR Redirect in Python entrypoint scripts
> ----------------------------------------------------------------
>
>                 Key: ATLAS-3557
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3557
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Mariusz Górski
>            Priority: Minor
>
> *Background*:
> Currently Atlas *entrypoint.sh* uses Python scripts for setup. Executing java process is done through *runProcess* function in *atlas_config.py*, which explicitly redirects *stdout* and *stderr* of those processes to files. We would like this to be configurable, so we are able to use bare log4j config to define our logging strategy. This way logging stream might be easily captured while running Atlas on Docker/Kubernetes, where containers stdout is captured.
>  
> *Proposal*:
> Adding optional *REDIRECT_STDOUT* env variable which defaults to *True* (for backwards compatibility):
>  * When *True* - nothing changes
>  * When *False* - runProcess is opening subprocess without stdout and stderr kwargs 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)