[ https://issues.apache.org/jira/browse/HADOOP-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923218#comment-13923218 ]
Arpit Agarwal commented on HADOOP-10391: ---------------------------------------- Thanks for reporting this Chris. The change in behavior was by design. However it should be fine to add a special case for "none". +[~benoyantony]. > HADOOP-10211 change for comma-separated list of QOP values broke > backwards-compatibility with existing configs. > --------------------------------------------------------------------------------------------------------------- > > Key: HADOOP-10391 > URL: https://issues.apache.org/jira/browse/HADOOP-10391 > Project: Hadoop Common > Issue Type: Bug > Components: security > Affects Versions: 2.4.0 > Reporter: Chris Nauroth > Priority: Blocker > > HADOOP-10211 changed parsing of QOP values to support a comma-separated list. > This change accidentally broke backwards-compatibility with existing > configs. Previously, an unrecognized value caused it to default to > authentication. Now, an unrecognized value causes > {{IllegalArgumentException}}. Some deployments had been using a value of > "none" in insecure clusters, so the change would break those existing > deployments. -- This message was sent by Atlassian JIRA (v6.2#6252)