Can I take Solr role (aggregator, searcher) into consideration at start-up?

instance in question is a searcher, not if it is an aggregator? At present the cache is loaded in the inform() function; is that the wrong place for it? Thanks in advance for your help. Jitka -- View this message in context: http://lucene.472066.n3.nabble.com/Can-I-take-Solr-role-aggregator

Re: using data from external service in Solr: value source or auxiliary core?

slow to be a viable option without caching. I am new to Solr caching, hence all the questions in my original post. Thanks again, Jitka On Mon, Mar 14, 2016 at 2:07 AM, Charlie Hull-3 [via Lucene] < ml-node+s472066n4263572...@n3.nabble.com> wrote: > On 11/03/2016 17:36, Jitka wrote:

using data from external service in Solr: value source or auxiliary core?

for your time and advice. Jitka

Re: search component needs access to results of previous component

Good question, Mikhail. I started by putting that logic in the prepare() function by sheer force of habit, but have since moved it first to distributedProcess() (my system is sharded) and now to handleResponses() (as in MoreLikeThisComponent.java, which I am mimicking without understanding). As

Re: search component needs access to results of previous component

Thanks for your reply. I'll check out that link. -- View this message in context: http://lucene.472066.n3.nabble.com/search-component-needs-access-to-results-of-previous-component-tp4138335p4139409.html Sent from the Solr - User mailing list archive at Nabble.com.

search component needs access to results of previous component

and are not available to the aggregator. Either I am going about this all wrong, or these must be standard problems for creators of custom QueryComponents. Are there standard solutions? Any feedback would be much appreciated. Thanks, Jitka -- View this message in context: http://lucene.472066.n3