[
https://issues.apache.org/jira/browse/KNOX-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-2186:
--------------------------------
Description:
With KNOX-2160, Knos is capable of processing a Hadoop XML configuration file
and turn its content into Knox providers.
It'd be beneficial to add support for the following use cases that are also
Cloudera Manager integration specific:
*1.)* Cloudera Manager reports if auto-discovery is {{enabled}} for each known
services. That is, a list of boolean properties can be generated by CM
indicating if {{SERVICE_X}} is enabled or not in the following form:
{{gateway.auto.discovery.enabled.SERVICE_NAME=[true|false]}}
The new Hadoop XML configuration parser should take this information into
account, and add a certain service into the generated Knox descriptor only if
that service is explicitly {{enabled}} or there is no boolean flag within the
CM generated properties with that service name (indicating an unknown - custom
- service)
*2.)* There are some services - mainly UI services - that are not working
without some more required services in place (mainly their API counterpart).
For instance: {{RANGERUI}} won't work properly if {{RANGER}} is not available.
The new Hadoop XML configuration parser should be modified to not to add any
service into the generated Knox descriptor unless
* all required services are available (if any)
* all required services are enabled (see the previous point)
was:
With KNOX-2160, Knos is capable of processing a Hadoop XML configuration file
and turn its content into Knox providers.
It'd be beneficial to add support for the following use case that is also
Cloudera manager integration specific:
*1.)* Cloudera Manager reports if auto-discovery is {{enabled}} for each known
services. That is, a list of boolean properties can be generated by CM
indicating if {{SERVICE_X}} is enabled or not in the following form:
{{gateway.auto.discovery.enabled.SERVICE_NAME=[true|false]}}
The new Hadoop XML configuration parser should take this information into
account, and add a certain service into the generated Knox descriptor only if
that service is explicitly {{enabled}} or there is no boolean flag within the
CM generated properties with that service name (indicating an unknown - custom
- service)
*2.)* There are some services - mainly UI services - that are not working
without some more required services in place (mainly their API counterpart).
For instance: {{RANGERUI}} won't work properly if {{RANGER}} is not available.
The new Hadoop XML configuration parser should be modified to not to add any
service into the generated Knox descriptor unless
* all required services are available (if any)
* all required services are enabled (see the previous point)
> Cloudera Manager integration - filter services
> ----------------------------------------------
>
> Key: KNOX-2186
> URL: https://issues.apache.org/jira/browse/KNOX-2186
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 1.4.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 1.4.0
>
>
> With KNOX-2160, Knos is capable of processing a Hadoop XML configuration file
> and turn its content into Knox providers.
> It'd be beneficial to add support for the following use cases that are also
> Cloudera Manager integration specific:
> *1.)* Cloudera Manager reports if auto-discovery is {{enabled}} for each
> known services. That is, a list of boolean properties can be generated by CM
> indicating if {{SERVICE_X}} is enabled or not in the following form:
> {{gateway.auto.discovery.enabled.SERVICE_NAME=[true|false]}}
> The new Hadoop XML configuration parser should take this information into
> account, and add a certain service into the generated Knox descriptor only if
> that service is explicitly {{enabled}} or there is no boolean flag within the
> CM generated properties with that service name (indicating an unknown -
> custom - service)
> *2.)* There are some services - mainly UI services - that are not working
> without some more required services in place (mainly their API counterpart).
> For instance: {{RANGERUI}} won't work properly if {{RANGER}} is not available.
> The new Hadoop XML configuration parser should be modified to not to add any
> service into the generated Knox descriptor unless
> * all required services are available (if any)
> * all required services are enabled (see the previous point)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
