You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Minder (JIRA)" <ji...@apache.org> on 2018/02/06 13:47:00 UTC
[jira] [Updated] (KNOX-1172) OOZIEUI service definition name
conflict
[ https://issues.apache.org/jira/browse/KNOX-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Minder updated KNOX-1172:
-------------------------------
Description:
The OOZIEUI service definition uses role/name OOZIEUI/oozie. There is some limitation causing a conflict with the service name between OOZIE/oozie and OOZIEUI/oozie. The functional issue caused by this is that the OOZIEUI rewrite rules are not applied.
The short term fix for this is to change the OOZIEUI service name to oozieui. Since service names are seldom (if ever) used there is unlikely to be a backwards compatibility issue. Further since the OOZIEUI service apparently will not work with this name the OOZIEUI service is not likely being used anyway.
For a longer term generalized fix I've filed KNOX-1173.
was:The OOZIEUI service definition uses role/name OOZIEUI/oozie. There is some limitation causing a conflict with the service name between OOZIE/oozie and OOZIEUI/oozie. The functional issue caused by this is that the OOZIEUI rewrite rules are not applied. The short term fix for this is to change the OOZIEUI service name to oozieui. Since service names are seldom (if ever) used there is unlikely to be a backwards compatibility issue. Further since the OOZIEUI service apparently will not work with this name the OOZIEUI service is not likely being used anyway.
> OOZIEUI service definition name conflict
> ----------------------------------------
>
> Key: KNOX-1172
> URL: https://issues.apache.org/jira/browse/KNOX-1172
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.14.0
> Reporter: Kevin Minder
> Assignee: Kevin Minder
> Priority: Major
> Fix For: 1.1.0
>
>
> The OOZIEUI service definition uses role/name OOZIEUI/oozie. There is some limitation causing a conflict with the service name between OOZIE/oozie and OOZIEUI/oozie. The functional issue caused by this is that the OOZIEUI rewrite rules are not applied.
> The short term fix for this is to change the OOZIEUI service name to oozieui. Since service names are seldom (if ever) used there is unlikely to be a backwards compatibility issue. Further since the OOZIEUI service apparently will not work with this name the OOZIEUI service is not likely being used anyway.
> For a longer term generalized fix I've filed KNOX-1173.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)