You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Denes Bodo (JIRA)" <ji...@apache.org> on 2019/01/21 10:04:00 UTC
[jira] [Commented] (SQOOP-3420) Invalid ERROR message initiates
false alarms
[ 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 file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)