[
https://issues.apache.org/jira/browse/SQOOP-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950985#comment-14950985
]
ASF subversion and git services commented on SQOOP-2606:
--------------------------------------------------------
Commit 38de9dde8ddd5cab1fa94d06bf3cac5e55ff457c in sqoop's branch
refs/heads/sqoop2 from [~hshreedharan]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=38de9dd ]
SQOOP-2606. Sqoop2: Do not reconfigure log4j if there are no log4j properties
inside sqoop.properties file
(Jarcec via Hari)
> Sqoop2: Do not reconfigure log4j if there are no log4j properties inside
> sqoop.properties file
> ----------------------------------------------------------------------------------------------
>
> Key: SQOOP-2606
> URL: https://issues.apache.org/jira/browse/SQOOP-2606
> Project: Sqoop
> Issue Type: Bug
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.7
>
> Attachments: SQOOP-2606.patch, SQOOP-2606.patch
>
>
> Current
> [SqoopConfiguration|https://github.com/apache/sqoop/blob/sqoop2/core/src/main/java/org/apache/sqoop/core/SqoopConfiguration.java#L283]
> implementation will assume that log4 is *always* configured inside
> {{sqoop.properties}} file and if this is not the case, then it will
> reconfigure log4j with "nothing". I like the ability to specify log4j
> properties inside the configuration file - that is very handy, however they
> are valid use cases when one would supply the log4j configuration using
> "usual" means and hence we should not re-configure log4j if there is no
> configuration inside the {{sqoop.properties}} file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
