You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Gabor Bota (Jira)" <ji...@apache.org> on 2020/03/04 15:56:00 UTC

[jira] [Assigned] (HADOOP-16745) S3Guard fsck: Use enum instead of int for severity in violations

     [ https://issues.apache.org/jira/browse/HADOOP-16745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabor Bota reassigned HADOOP-16745:
-----------------------------------

    Assignee:     (was: Gabor Bota)

> S3Guard fsck: Use enum instead of int for severity in violations
> ----------------------------------------------------------------
>
>                 Key: HADOOP-16745
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16745
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Gabor Bota
>            Priority: Major
>
> Looking in the code, I can see that it's a severity level "2", so not that serious.
> # We should go away from and int value here to something comprehensible, i.e. an enum.
> # Or at least some contents used in the Violation enum setup.
> # Either way, how about letting us choose which level to fail on.
> # And maybe severity 2 should be logged at WARN, not ERROR, as an early user was confused "why an error yet none reported in status"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org