[
https://issues.apache.org/jira/browse/KNOX-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523195#comment-14523195
]
Rick Kellogg commented on KNOX-528:
-----------------------------------
In the short term, we are restricted to SOLR 4.10.2 as that is what is included
in HortonWorks Search at this time. Longer term we will upgrade to SOLR 5.x
which includes many enhancements plus increased maximum core capacity.
The client within SOLR 4.x is HttpSolrServer and has been renamed to
HttpSolrClient in 5.x. I think this would be the preferred client in both
cases and would expect both to be compatible from a Knox standpoint. I might
be wrong here.
Just reviewed the SOLR Collections API
(https://cwiki.apache.org/confluence/display/solr/Collections+API), I see the
complications. Knox would turn into a sort of federation of clusters and
therefore need to know which cores are located in specific clusters. Fairly
tricky issue in terms of features ownership. We definitely do not want to
replicate features that SOLR Cloud might address in the future. Will do a bit
more research and provide input.
> Support for Apache SOLR REST APIs
> ---------------------------------
>
> Key: KNOX-528
> URL: https://issues.apache.org/jira/browse/KNOX-528
> Project: Apache Knox
> Issue Type: Improvement
> Reporter: Rick Kellogg
> Fix For: 0.7.0
>
>
> Add Knox support for routing and securing Apache SOLR's REST APIs
> See: https://wiki.apache.org/solr/Solrj
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
