An update:
Another idea comes from Erick Hatcher; sharing it for the benefit of anyone
who's interested in the topic:
maybe you can make a custom request handler that toggles
which is the default chain?
On Mon, Nov 3, 2014 at 4:08 PM, Dmitry Kan wrote:
> Thanks, Mike,
>
> we have discussed
Thanks, Mike,
we have discussed something similar with steffkes on IRC today, where I
said: "some programmatic convenience would be great of course. But I could
in principle imagine having two versions of solrconfig.xml and swapping
them followed by a core reload. It just sounds a bit scary to me.
Just to get the obvious sledgehammer solution out of the way - upload a
new, edited solrconfig.xml with the default changed, and reload the core.
-Mike
On 11/3/14 6:28 AM, Dmitry Kan wrote:
Hello solr fellows,
I'm working on a project that involves using two update chains. One default
chain
Hello solr fellows,
I'm working on a project that involves using two update chains. One default
chain is used most of the time and another one custom is used sporadically.
The default update chain is called automatically without action needed
(well, that's why it is default).
The custom pipeline
