Is there any way I can get the cores and do my initialization in the @Override 
public void init(final NamedList args) method?  I could wait for the first 
request, but I imagine I'd have to deal with indexing requests piling up while 
I iterate over every document in every index.

Ryan
________________________________________
From: Mark Miller [markrmil...@gmail.com]
Sent: Tuesday, February 05, 2013 1:15 PM
To: solr-user@lucene.apache.org
Subject: Re: Correct way for getting SolrCore?

The request should give you access to the core - the core to the core 
descriptor, the descriptor to the core container, which knows about all the 
cores.

- Mark

On Feb 5, 2013, at 4:09 PM, Ryan Josal <rjo...@rim.com> wrote:

> Hey guys,
>
>  I am writing an UpdateRequestProcessorFactory plugin which needs to have 
> some initialization code in the init method.  I need to build some 
> information about each SolrCore in memory so that when an update comes in for 
> a particular SolrCore, I can use the data for the appropriate core.  
> Ultimately, I need a lucene IndexReader for each core.  I figure I'd get this 
> through a SolrCore, CoreContainer, or CoreDescriptor.  I've looked around for 
> awhile and I always end up going in circles.  So how can I iterate over cores 
> that have been loaded?
>
> Ryan
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential 
> information, privileged material (including material protected by the 
> solicitor-client or other applicable privileges), or constitute non-public 
> information. Any use of this information by anyone other than the intended 
> recipient is prohibited. If you have received this transmission in error, 
> please immediately reply to the sender and delete this information from your 
> system. Use, dissemination, distribution, or reproduction of this 
> transmission by unintended recipients is not authorized and may be unlawful.


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

Reply via email to