[
https://issues.apache.org/jira/browse/STANBOL-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler resolved STANBOL-353.
-----------------------------------------
Resolution: Fixed
As of #1205331 there is now a new Component called
"SolrServerPublishingComponent" that publishes all CoreContainer instances with
the property "org.apache.solr.core.CoreContainer.publishREST" set to "true"
under a configurable path on the Stanbol RESTful interface (default is
/solr/{server-name}). This removes the requirement to explicitly configure the
path for a CoreContainer by using the Whiteboard pattern.
To publish a specific CoreContainer under a different path one can still use
the previously used "SolrDispatchFilterComponent" and set the
"org.apache.solr.core.CoreContainer.publishREST" for this CoreContainer to
"false" to deactivate publishing for this core on the default location.
With this additions I consider this Issue as solved. If we need/want to publish
single cores or only specific request handlers (e.g. deactivating the /admin
handlers) I suggest to create an new Issue.
> 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
