[
https://issues.apache.org/jira/browse/STANBOL-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145316#comment-13145316
]
Rupert Westenthaler commented on STANBOL-353:
---------------------------------------------
As of #1195450 the RESTful interface of Solr CoreContainer can be mapped to the
HttpService of the OSGI environment by the use of a special variant (subclass)
of the SolrDispatchFilter that uses the CoreContainer registered as OSGI servie
instead of initializing a new one on the initialisation of the Filter (as it is
the case for the std. SolrDispatchFilter).
Currently a OSGI component is provided that can be used to publish
CoreContainers on a configured path. In future there will be also the
possibility to publish CoreContainer "automatically" under a configurable
global prefix (e.g. "/solr") without the need of any further configuration.
This auto-publish feature can be (de)activated by a boolean property in the
metadata of the service registration for a CoreContainer.
CoreContainers published this way will be available under
{globalPrefix}/{coreContainer-name}/{solrCore-name}/select?q=test
> Make the RESTful API internally Managed SolrCores available via the Stanbol
> http endpoint
> -----------------------------------------------------------------------------------------
>
> Key: STANBOL-353
> URL: https://issues.apache.org/jira/browse/STANBOL-353
> Project: Stanbol
> Issue Type: New Feature
> Components: Commons
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> Currently SolrCors managed by the org.apache.commons.solr module are only
> exposed as EmbeddedSolrServer. There is no possibility to access such
> SolrCores via the typical RESTful API.
> This will include two improvements:
> (1) provide a Default JAX-RS resource that publishes all internally managed
> SolrCores at a specified Path.
> Also add a configuration that allows to enable/disable this feature.
> (2) provide a base implementation of a JAX-RS resource that allows to publish
> the RESTful API of a specific SolrCore.
> This is intended to be used by Modules that internally manage a SolrCore and
> want to have the RESTful API of the SolrServer to be available at a specific
> path or even to intercept calls (e.g. to do some preprocessing) before
> sending them to the SolrCore.
> For the implementation of this one needs something like
> org.apache.solr.servlet.SolrDispatchFilter but more flexible and configurable
> e.g.
> * allow only some core (e.g. cores that are configured to be published as
> RESTful service) - needed for (1)
> * allow initialization for a specific core - needed for (2)
> * allow to restrict the allowed RequestHandler (e.g. to disallow Admin
> Requests to prevent reconfiguration of the Solr via the RESTful API)
> In addition features already provided by JAX-RS should be also used by such
> an implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
