[
https://issues.apache.org/jira/browse/KNOX-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860451#comment-15860451
]
Richard Ding commented on KNOX-841:
-----------------------------------
Hi [~lmccay], thanks for comments that raise a good question: should Knox
define one service or two services in the case where REST API and UI share the
same endpoint.
An example is Oozie which defines two services in Knox (OOZIE and OOZIEUI). For
Solr, there were discussions in KNOX-528 about the merits of using separate
services for SOLR and SOLRUI.
I can see both pros and cons of using a single service vs two services. For
example, UI rewrite rules usually include OUTbound rules (filters) that are not
needed in REST API calls. With REST API calls, no outbound parsing is required.
OTOH, these two service can not colocate in the same topology and users must
define a separate topology for UI.
I prefer to use two services--one for REST API and one for UI. But I'm open to
create a patch under the same solr directory.
> Proxy support for Solr UI
> -------------------------
>
> Key: KNOX-841
> URL: https://issues.apache.org/jira/browse/KNOX-841
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 0.10.0
> Reporter: Richard Ding
> Assignee: Richard Ding
> Fix For: 0.12.0
>
> Attachments: KNOX_841_1.patch, KNOX-841_2.patch, KNOX_841.patch,
> Screen Shot 2017-02-05 at 3.01.20 PM.png
>
>
> Provide proxy UI support for the Solr UI.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
