I think it may already be a pipeline option on the Java side. I'd rather minimize the number of environment variables we are using to control behavior, but I haven't looked at how hard it is to plumb this through.
On Mon, Sep 24, 2018 at 2:21 PM Thomas Weise (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/BEAM-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625743#comment-16625743 > ] > > Thomas Weise commented on BEAM-5468: > ------------------------------------ > > I was also planning to look at this. My idea was to add another > environment variable so this can be controlled from the job bundle factory > / environment manager, and it can follow the logging level on the runner > side. Do you think this should be a pipeline option instead? > > > Allow runner to set worker log level in Python SDK harness. > > ----------------------------------------------------------- > > > > Key: BEAM-5468 > > URL: https://issues.apache.org/jira/browse/BEAM-5468 > > Project: Beam > > Issue Type: Improvement > > Components: sdk-py-harness > > Reporter: Robert Bradshaw > > Assignee: Robert Bradshaw > > Priority: Major > > > > > > > -- > This message was sent by Atlassian JIRA > (v7.6.3#76005) >
