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

Steve Loughran updated HADOOP-16745:
------------------------------------
    Description: 
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"

  was:
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 I was confused 
"why an error yet none reported in status"


> 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
>            Assignee: 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to