[
https://issues.apache.org/jira/browse/KNOX-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783265#comment-13783265
]
Larry McCay commented on KNOX-176:
----------------------------------
Obviously, there is name collision issue there.
We may need to add a <provider-param> element that identifies the provider to
override and contains <param>s.
It also leads to a larger question of whether providers should be configurable
or selectable at the service level.
Currently, we have global (cluster global) provider configuration.
It is conceivable that someone may want one provider for authorization for
webhdfs and another for webhcat someday.
> Per Service overrides of Provider parameters
> --------------------------------------------
>
> Key: KNOX-176
> URL: https://issues.apache.org/jira/browse/KNOX-176
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 0.3.0
> Reporter: Kevin Minder
> Fix For: 0.4.0
>
>
> Within the topology file it should be possible to override some of the
> provider params at the service level. The complicating factor is figuring
> how what filters should be setup with the service's params. Should the param
> names be prefixed with a provider's role and name?
> <topology>
> <gateway>
> <provider>
> <role>X</role?
> <param><name>Y</name><value>Z</value></param>
> </provider>
> </gateway>
> <service>
> <role>A</role>
> <param><name>Y</name><value>Z</value></param>
> </service>
> </topology>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
