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

Posted to dev@gobblin.apache.org by "Abhishek Tiwari (JIRA)" <ji...@apache.org> on 2017/08/11 06:07:00 UTC

[jira] [Resolved] (GOBBLIN-192) Gobblin AWS hardcodes the log4j config

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

Abhishek Tiwari resolved GOBBLIN-192.
-------------------------------------
    Resolution: Fixed

Issue resolved by pull request #2043
[https://github.com/apache/incubator-gobblin/pull/2043]

> Gobblin AWS hardcodes the log4j config
> --------------------------------------
>
>                 Key: GOBBLIN-192
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-192
>             Project: Apache Gobblin
>          Issue Type: Bug
>            Reporter: Joel Baranick
>            Assignee: Joel Baranick
>
> The current implementation of `GobblinAWSTaskRunner` and `GobblinAWSClusterManager` hardcode the log4j configuration.  This makes it difficult to bootstrap the AWS cluster outside of the `GobblinAWSClusterLauncher`.  `GobblinAWSTaskRunner` and `GobblinAWSClusterManager`  should be changed to use the embedded log4j configuration only if the configuration is not specified on the command line.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)