[ 
https://issues.apache.org/jira/browse/SOLR-16959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vincent Primault updated SOLR-16959:
------------------------------------
    Description: 
I would like to be able to hook into the process of discovering and persisting 
core descriptors. This allows to work with core descriptors not stored locally, 
or replicated elsewhere.

For this purpose, I propose to make the CoresLocator instance configurable, 
pretty much like other services (e.g., ConfigSetService, some handlers) are 
already configurable. Attached PR creates a new "coresContainer" parameter in 
solr.xml in order to achieve this. Because it is created outside of the 
CoreContainer (it is needed to load a CoreContainer), constructor of a custom 
CoresLocator receives a NodeConfig object (and not a CoreContainer) that it can 
use to lookup other parameters, if required.

Example usage:
{code:java}
<solr>
    <str name="coresLocator">com.myorg.CustomCoresLocator</str>
</solr>{code}

  was:
I would like to be able to hook into the process of discovering and persisting 
core descriptors. This allows to work with core descriptors not stored locally, 
or replicated elsewhere.

For this purpose, I propose to make the CoresLocator instance configurable, 
pretty much like other services are already configurable. Attached PR creates a 
new "coresContainer" parameter in solr.xml in order to achieve this:
{code:java}
<solr>
    <str name="coresLocator">com.myorg.CustomCoresLocator</str>
</solr>{code}
Because it is created outside of the CoreContainer (it is needed to load a 
CoreContainer), constructor of a custom CoresLocator receives a NodeConfig 
object (and not a CoreContainer) that it can use to lookup other parameters, if 
required.


> Make CoresContainer class configurable
> --------------------------------------
>
>                 Key: SOLR-16959
>                 URL: https://issues.apache.org/jira/browse/SOLR-16959
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Plugin system
>            Reporter: Vincent Primault
>            Priority: Minor
>
> I would like to be able to hook into the process of discovering and 
> persisting core descriptors. This allows to work with core descriptors not 
> stored locally, or replicated elsewhere.
> For this purpose, I propose to make the CoresLocator instance configurable, 
> pretty much like other services (e.g., ConfigSetService, some handlers) are 
> already configurable. Attached PR creates a new "coresContainer" parameter in 
> solr.xml in order to achieve this. Because it is created outside of the 
> CoreContainer (it is needed to load a CoreContainer), constructor of a custom 
> CoresLocator receives a NodeConfig object (and not a CoreContainer) that it 
> can use to lookup other parameters, if required.
> Example usage:
> {code:java}
> <solr>
>     <str name="coresLocator">com.myorg.CustomCoresLocator</str>
> </solr>{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to