You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (Created) (JIRA)" <ji...@apache.org> on 2011/11/07 11:57:51 UTC
[jira] [Created] (STANBOL-376) Improvements to SolrServerProvides
Improvements to SolrServerProvides
----------------------------------
Key: STANBOL-376
URL: https://issues.apache.org/jira/browse/STANBOL-376
Project: Stanbol
Issue Type: Improvement
Components: Commons
Reporter: Rupert Westenthaler
Assignee: Rupert Westenthaler
SolrServerProviders[1] are used to get clients for SolrServers based on the access uri. In case of "http" clients based on the RESTful interface of Solr are constructed. In other cases an EmbeddedSolrServer instance is created.
two improvements are planed as part of this:
1. move this service form the commons.solr.core to an own artifact with the name "org.apache.stanbol.commons.solr.provides"
2. make the EmbeddedSolrServerProvider[2] fully take advantage of STANBOL-354: Currently only for relatives paths CoreContainers are looked up as OSGI services. If an absolute path is parsed this components initializes and managed its own CoreContainers. This feature allowed to use Solr directories that where not managed by Stanbol. However with the current implementation such Solr CoreContainers and their SolrCores are not registered as OSGI.
The proposal is to define a new OSGI component called "ReferencedSolrServer" that allows to explicitly register such directories (e.g. by configuring an instance of this Component via the Apache Felix WebConsole). By that the EmbeddedSolrServerProvider would only need to lookup CoreContainer and SolrCores for parsed paths as OSGI services and would no longer need to internally manage CoreContainers.
In addition this change would also allow to provide the RESTful API of such - referenced - Solr CoreContainers via the HttpService of the OSGI environment running Stanbol (as described by STANBOL-343.
[1] http://svn.apache.org/viewvc/incubator/stanbol/trunk/commons/solr/core/src/main/java/org/apache/stanbol/commons/solr/SolrServerProviderManager.java?revision=1186726&view=markup
[2] http://svn.apache.org/viewvc/incubator/stanbol/trunk/commons/solr/core/src/main/java/org/apache/stanbol/commons/solr/impl/EmbeddedSolrPorovider.java?revision=1195450&view=markup
--
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
[jira] [Resolved] (STANBOL-376) Improvements to SolrServerProvides
Posted by "Rupert Westenthaler (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler resolved STANBOL-376.
-----------------------------------------
Resolution: Not A Problem
With revision #1206372 the SolrServerProviders where removed altogether.
Support for providing SolrServers for remote indexes was removed (Users can use SolrJ for that). Support for creating EmbeddedSolrServer has chanted significantly now that CoreContainer and SolrCores are registered OSGI services.
Users can use the normal OSGI to lookup and track OSGI services and than create an EmbeddedSolrServer instance.
In addition for tracking local SolrServers the new RegisteredSolrServerTracker utility was introduced.
> Improvements to SolrServerProvides
> ----------------------------------
>
> Key: STANBOL-376
> URL: https://issues.apache.org/jira/browse/STANBOL-376
> Project: Stanbol
> Issue Type: Improvement
> Components: Commons
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> SolrServerProviders[1] are used to get clients for SolrServers based on the access uri. In case of "http" clients based on the RESTful interface of Solr are constructed. In other cases an EmbeddedSolrServer instance is created.
> two improvements are planed as part of this:
> 1. move this service form the commons.solr.core to an own artifact with the name "org.apache.stanbol.commons.solr.provides"
> 2. make the EmbeddedSolrServerProvider[2] fully take advantage of STANBOL-354: Currently only for relatives paths CoreContainers are looked up as OSGI services. If an absolute path is parsed this components initializes and managed its own CoreContainers. This feature allowed to use Solr directories that where not managed by Stanbol. However with the current implementation such Solr CoreContainers and their SolrCores are not registered as OSGI.
> The proposal is to define a new OSGI component called "ReferencedSolrServer" that allows to explicitly register such directories (e.g. by configuring an instance of this Component via the Apache Felix WebConsole). By that the EmbeddedSolrServerProvider would only need to lookup CoreContainer and SolrCores for parsed paths as OSGI services and would no longer need to internally manage CoreContainers.
> In addition this change would also allow to provide the RESTful API of such - referenced - Solr CoreContainers via the HttpService of the OSGI environment running Stanbol (as described by STANBOL-353.
> [1] http://svn.apache.org/viewvc/incubator/stanbol/trunk/commons/solr/core/src/main/java/org/apache/stanbol/commons/solr/SolrServerProviderManager.java?revision=1186726&view=markup
> [2] http://svn.apache.org/viewvc/incubator/stanbol/trunk/commons/solr/core/src/main/java/org/apache/stanbol/commons/solr/impl/EmbeddedSolrPorovider.java?revision=1195450&view=markup
--
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
[jira] [Updated] (STANBOL-376) Improvements to SolrServerProvides
Posted by "Rupert Westenthaler (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STANBOL-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Westenthaler updated STANBOL-376:
----------------------------------------
Description:
SolrServerProviders[1] are used to get clients for SolrServers based on the access uri. In case of "http" clients based on the RESTful interface of Solr are constructed. In other cases an EmbeddedSolrServer instance is created.
two improvements are planed as part of this:
1. move this service form the commons.solr.core to an own artifact with the name "org.apache.stanbol.commons.solr.provides"
2. make the EmbeddedSolrServerProvider[2] fully take advantage of STANBOL-354: Currently only for relatives paths CoreContainers are looked up as OSGI services. If an absolute path is parsed this components initializes and managed its own CoreContainers. This feature allowed to use Solr directories that where not managed by Stanbol. However with the current implementation such Solr CoreContainers and their SolrCores are not registered as OSGI.
The proposal is to define a new OSGI component called "ReferencedSolrServer" that allows to explicitly register such directories (e.g. by configuring an instance of this Component via the Apache Felix WebConsole). By that the EmbeddedSolrServerProvider would only need to lookup CoreContainer and SolrCores for parsed paths as OSGI services and would no longer need to internally manage CoreContainers.
In addition this change would also allow to provide the RESTful API of such - referenced - Solr CoreContainers via the HttpService of the OSGI environment running Stanbol (as described by STANBOL-353.
[1] http://svn.apache.org/viewvc/incubator/stanbol/trunk/commons/solr/core/src/main/java/org/apache/stanbol/commons/solr/SolrServerProviderManager.java?revision=1186726&view=markup
[2] http://svn.apache.org/viewvc/incubator/stanbol/trunk/commons/solr/core/src/main/java/org/apache/stanbol/commons/solr/impl/EmbeddedSolrPorovider.java?revision=1195450&view=markup
was:
SolrServerProviders[1] are used to get clients for SolrServers based on the access uri. In case of "http" clients based on the RESTful interface of Solr are constructed. In other cases an EmbeddedSolrServer instance is created.
two improvements are planed as part of this:
1. move this service form the commons.solr.core to an own artifact with the name "org.apache.stanbol.commons.solr.provides"
2. make the EmbeddedSolrServerProvider[2] fully take advantage of STANBOL-354: Currently only for relatives paths CoreContainers are looked up as OSGI services. If an absolute path is parsed this components initializes and managed its own CoreContainers. This feature allowed to use Solr directories that where not managed by Stanbol. However with the current implementation such Solr CoreContainers and their SolrCores are not registered as OSGI.
The proposal is to define a new OSGI component called "ReferencedSolrServer" that allows to explicitly register such directories (e.g. by configuring an instance of this Component via the Apache Felix WebConsole). By that the EmbeddedSolrServerProvider would only need to lookup CoreContainer and SolrCores for parsed paths as OSGI services and would no longer need to internally manage CoreContainers.
In addition this change would also allow to provide the RESTful API of such - referenced - Solr CoreContainers via the HttpService of the OSGI environment running Stanbol (as described by STANBOL-343.
[1] http://svn.apache.org/viewvc/incubator/stanbol/trunk/commons/solr/core/src/main/java/org/apache/stanbol/commons/solr/SolrServerProviderManager.java?revision=1186726&view=markup
[2] http://svn.apache.org/viewvc/incubator/stanbol/trunk/commons/solr/core/src/main/java/org/apache/stanbol/commons/solr/impl/EmbeddedSolrPorovider.java?revision=1195450&view=markup
> Improvements to SolrServerProvides
> ----------------------------------
>
> Key: STANBOL-376
> URL: https://issues.apache.org/jira/browse/STANBOL-376
> Project: Stanbol
> Issue Type: Improvement
> Components: Commons
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
>
> SolrServerProviders[1] are used to get clients for SolrServers based on the access uri. In case of "http" clients based on the RESTful interface of Solr are constructed. In other cases an EmbeddedSolrServer instance is created.
> two improvements are planed as part of this:
> 1. move this service form the commons.solr.core to an own artifact with the name "org.apache.stanbol.commons.solr.provides"
> 2. make the EmbeddedSolrServerProvider[2] fully take advantage of STANBOL-354: Currently only for relatives paths CoreContainers are looked up as OSGI services. If an absolute path is parsed this components initializes and managed its own CoreContainers. This feature allowed to use Solr directories that where not managed by Stanbol. However with the current implementation such Solr CoreContainers and their SolrCores are not registered as OSGI.
> The proposal is to define a new OSGI component called "ReferencedSolrServer" that allows to explicitly register such directories (e.g. by configuring an instance of this Component via the Apache Felix WebConsole). By that the EmbeddedSolrServerProvider would only need to lookup CoreContainer and SolrCores for parsed paths as OSGI services and would no longer need to internally manage CoreContainers.
> In addition this change would also allow to provide the RESTful API of such - referenced - Solr CoreContainers via the HttpService of the OSGI environment running Stanbol (as described by STANBOL-353.
> [1] http://svn.apache.org/viewvc/incubator/stanbol/trunk/commons/solr/core/src/main/java/org/apache/stanbol/commons/solr/SolrServerProviderManager.java?revision=1186726&view=markup
> [2] http://svn.apache.org/viewvc/incubator/stanbol/trunk/commons/solr/core/src/main/java/org/apache/stanbol/commons/solr/impl/EmbeddedSolrPorovider.java?revision=1195450&view=markup
--
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