[
https://issues.apache.org/jira/browse/SQOOP-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575553#comment-13575553
]
Hudson commented on SQOOP-875:
------------------------------
Integrated in Sqoop2-hadoop200 #187 (See
[https://builds.apache.org/job/Sqoop2-hadoop200/187/])
SQOOP-875: ClassUtils.instantiate class should not be logging on ERROR
level (Revision e8ca6f6c93cf193bd6842746e4e9df5d9f85f8d5)
Result = SUCCESS
cheolsoo :
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=e8ca6f6c93cf193bd6842746e4e9df5d9f85f8d5
Files :
* common/src/main/java/org/apache/sqoop/utils/ClassUtils.java
> Sqoop2: ClassUtils.instantiate class should not be logging on ERROR level
> -------------------------------------------------------------------------
>
> Key: SQOOP-875
> URL: https://issues.apache.org/jira/browse/SQOOP-875
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.1
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Priority: Trivial
> Fix For: 1.99.2
>
> Attachments: bugSQOOP-875.patch
>
>
> ClassUtils was designed to handle gracefully all error conditions and it's
> return null on every issue. Method loadClass already logs on debug level, but
> method instantiate logs on ERROR level. I believe that we should change that
> to debug level as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
