[
https://issues.apache.org/jira/browse/HADOOP-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth resolved HADOOP-10391.
------------------------------------
Resolution: Won't Fix
I'm resolving this as won't fix. I agree with the comments from Arpit and
Daryn that the stricter validation introduced in HADOOP-10211 is a good thing.
I agree that the old behavior was a bug, so there is less onus to support it
from a backwards-compatibility perspective.
I do think it's important to publish a release note, so I added that to
HADOOP-10211. Could someone who worked the original issue please review what I
entered? Feel free to make changes to the content as you see fit.
Thank you, everyone, and sorry for the distraction.
> 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
> Assignee: Benoy Antony
> 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)
