sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denes Bodo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3420) Invalid ERROR message initiates false alarms
Date Mon, 21 Jan 2019 10:04:00 GMT

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

Denes Bodo commented on SQOOP-3420:

[~ericlin], [~vasas], [~vasubramanian] Do you think it should be *info* level or a *warn*
is more suitable in this case?
 * Former level was debug, so it shall not be *warn*.
 * This message is printed when Sqoop cannot perform a backup operation so *warn* level
is more suitable in this case.

If any of us has more experience in operation and has connection with real life users: what
would be the better message type?

> 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
>            Priority: Critical
>              Labels: usability
> 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

This message was sent by Atlassian JIRA

View raw message