sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3420) Invalid ERROR message initiates false alarms
Date Fri, 01 Feb 2019 16:30:00 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758476#comment-16758476
] 

Hudson commented on SQOOP-3420:
-------------------------------

SUCCESS: Integrated in Jenkins build Sqoop-hadoop200 #1251 (See [https://builds.apache.org/job/Sqoop-hadoop200/1251/])
SQOOP-3420: Invalid ERROR message initiates false alarms (ferroriuss: [https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=5ab5190304d0e13d1c5eaa56d1f486f3106529d3])
* (edit) src/java/org/apache/sqoop/orm/CompilationManager.java


> Invalid ERROR message initiates false alarms
> --------------------------------------------
>
>                 Key: SQOOP-3420
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3420
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.4.7
>            Reporter: Denes Bodo
>            Assignee: Denes Bodo
>            Priority: Critical
>              Labels: usability
>         Attachments: SQOOP-3420_001.patch
>
>
> In SQOOP-3042, a debug message was refactored to be error instead means false alarms
in customer log analyser. After understanding the functionality it is recommended to use info
level message instead of error in case when ImportTool is unable to backup generated .java
file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message