the
type of purpose you are using it for.
:
:
: -S
:
: -Original Message-
: From: Chris Hostetter [mailto:hossman_luc...@fucit.org]
: Sent: Friday, June 30, 2017 1:34 PM
: To: solr-user
: Subject: [EXTERNAL] - Re: custom search component process method not called
:
:
: :
: : I believ
June 30, 2017 1:34 PM
To: solr-user
Subject: [EXTERNAL] - Re: custom search component process method not called
:
: I believe the init bit is called on startup, so that leaves the second
: part of your puzzle. I find this a bit suspicious though:
:
:${solr.core.name}
:
: Are you sure th
, June 30, 2017 1:26 PM
To: solr-user
Subject: [EXTERNAL] - Re: custom search component process method not called
I believe the init bit is called on startup, so that leaves the second part of
your puzzle. I find this a bit suspicious though:
${solr.core.name}
Are you sure this is different for
:
: I believe the init bit is called on startup, so that leaves the second
: part of your puzzle. I find this a bit suspicious though:
:
:${solr.core.name}
:
: Are you sure this is different for all three cores? My thought is that
: the component is being called for all three cores but it's
I believe the init bit is called on startup, so that leaves the second
part of your puzzle. I find this a bit suspicious though:
${solr.core.name}
Are you sure this is different for all three cores? My thought is that
the component is being called for all three cores but it's hard to see
b/c t
I have a custom search component that registered in the last-components list
for /select. The component does some bookkeeping. I got it working using a
helloworld core using one of the example datasets.
I have a few logging statements to monitor the custom processing. I have the
jar with my c
