You need to back up a bit. Specifying an update chain for /select makes
no sense, they are orthogonal.
See the section "Update Request Processor Configuration” in the reference
guide. Basically you need to define your own update processor chain
and make sure your custom stuff preceeds the
Distribu
HI Eric,
Thanks for detailed explanation.
How can i find that update processor chain is preproces or post process ? i
have configured the update chain processor in for . I am sure this is working as preprocess
for me. i just would like to learn how can i add post process doc steps in
my solr config
Why am I getting this email? Who are all BCC-ed?
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Thursday, March 7, 2019 10:33 AM
To: solr-user@lucene.apache.org
Subject: Re: TrieDate field in UpdateRequestProcessorChain
bq. should be fine as update chain
bq. should be fine as update chain process is pre-process of document indexing.
You may be confusing document _routing_ with document _indexing_.
When a document comes in to Solr, the first thing that happens is the doc
is examined and the ID is used to route the raw document to the appropriate
Hi Eric,
Thanks for your response.
Yes, we are using solr cloud. i understood your point and has been
considered while designing unique id. unique id (i.e Id) is set using
update processor chain only and believe this should be fine as update chain
process is pre-process of document indexing.
Cou
I’d probably go with a StatelessScriptUpdateProcessorFactory. It allows you to
manipulate the incoming doc in whatever scripting language you have access to,
javascript, groovy, etc.
Do be aware though that if your using SolrCloud and the id field is also the
you have to be very careful to do
