sqoop-dev mailing list archives

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

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

ASF subversion and git services commented on SQOOP-3420:
--------------------------------------------------------

Commit 5ab5190304d0e13d1c5eaa56d1f486f3106529d3 in sqoop's branch refs/heads/trunk from Denes
Bodo
[ https://gitbox.apache.org/repos/asf?p=sqoop.git;h=5ab5190 ]

SQOOP-3420: Invalid ERROR message initiates false alarms

(Denes Bodo via Fero Szabo)

> 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