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 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 can be switched on using update.chain http parameter,
like so:
[code]
UpdateRequest updateRequest = new UpdateRequest();
updateRequest.setCommitWithin(10000);
updateRequest.setParam("update.chain", "customupdatechain");
updateRequest.add(solrDoc);
updateRequest.process(solrServer);
[/code]
Now I have a new requirement: be able to install the custom chain as the
default update chain such that any client that is sending data in will get
it processed via the custom chain and not the default chain. And this
should happen seamlessly to the client, i.e. no parameter change needed.
Is this possible with the current state of the Solr core / collection api
or some other method?
