[
https://issues.apache.org/jira/browse/HADOOP-14785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674512#comment-16674512
]
Steve Loughran commented on HADOOP-14785:
-----------------------------------------
Thinking some more.
h2. Whichever comes last wins; if an opt() entrie follows a must(), the
configuration parameter is downgraded to optional
Because its the only way to address duplicat must or opt entries, we should do
the same for them everywhere.
As this is the current behaviour, closing as a WORKSFORME
> Specify the behavior of handling conflicts between must and opt parameters
> ---------------------------------------------------------------------------
>
> Key: HADOOP-14785
> URL: https://issues.apache.org/jira/browse/HADOOP-14785
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs
> Affects Versions: 3.0.0-alpha3
> Reporter: Lei (Eddy) Xu
> Priority: Major
>
> It is flexible to allow user to use strings as key/values to specify the
> behaviors of {{FSOutputStream}}, but this flexibility offers the potential
> conflicts between parameters.
> It should specify a general rule of how to handle such conflicts for differnt
> file system implementations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
