How are URP's managed with respect to cloud deployment? Given some
solrconfig.xml like the below, do I expect it to be in the chain on
the leader, the shards, or both?

   <updateRequestProcessorChain name="RNI">
    <!-- some day, add parameters when we have some -->
    <processor class="com.basistech.rni.solr.NameIndexingUpdateRequestProcessorFactory"/>
    <processor class="solr.LogUpdateProcessorFactory" />
    <processor class="solr.DistributedUpdateProcessorFactory"/>
    <processor class="solr.RunUpdateProcessorFactory" />
  </updateRequestProcessorChain>

    <!-- activate RNI processing by adding the RNI URP to the chain
for xml updates -->
  <requestHandler name="/update"
                  class="solr.XmlUpdateRequestHandler">
    <lst name="defaults">
      <str name="update.chain">RNI</str>
    </lst>
    </requestHandler>

In this case on each node, order matters. If you, for example, define a
 standard SignatureUpdateProcessorFactory before the
 DistributedUpdateProcessorFactory you will end up with multiple values
 for the signature field.

 On Tue, 10 Apr 2012 12:43:36 -0400, Benson Margulies
 <[EMAIL PROTECTED]> wrote:
> How are URP's managed with respect to cloud deployment? Given some
> solrconfig.xml like the below, do I expect it to be in the chain on
> the leader, the shards, or both?
>
>    <updateRequestProcessorChain name="RNI">
>     <!-- some day, add parameters when we have some -->
>     <processor
>
> class="com.basistech.rni.solr.NameIndexingUpdateRequestProcessorFactory"/>
>     <processor class="solr.LogUpdateProcessorFactory" />
>     <processor class="solr.DistributedUpdateProcessorFactory"/>
>     <processor class="solr.RunUpdateProcessorFactory" />
>   </updateRequestProcessorChain>
>
>     <!-- activate RNI processing by adding the RNI URP to the chain
> for xml updates -->
>   <requestHandler name="/update"
>                   class="solr.XmlUpdateRequestHandler">
>     <lst name="defaults">
>       <str name="update.chain">RNI</str>
>     </lst>
>     </requestHandler>

--
 Markus Jelsma - CTO - Openindex
 http://www.linkedin.com/in/markus17
 050-8536600 / 06-50258350

On Tue, Apr 10, 2012 at 1:08 PM, Markus Jelsma
<[EMAIL PROTECTED]> wrote:
> In this case on each node, order matters. If you, for example, define a
> standard SignatureUpdateProcessorFactory before the
> DistributedUpdateProcessorFactory you will end up with multiple values for
> the signature field.

That seems to imply that 'before' processors run both on the leader
and on the shards. Where do the afters run? Just on the leader or just
on the shards?

>
>
> On Tue, 10 Apr 2012 12:43:36 -0400, Benson Margulies <[EMAIL PROTECTED]>
> wrote:
>>
>> How are URP's managed with respect to cloud deployment? Given some
>> solrconfig.xml like the below, do I expect it to be in the chain on
>> the leader, the shards, or both?
>>
>>   <updateRequestProcessorChain name="RNI">
>>    <!-- some day, add parameters when we have some -->
>>    <processor
>>
>> class="com.basistech.rni.solr.NameIndexingUpdateRequestProcessorFactory"/>
>>    <processor class="solr.LogUpdateProcessorFactory" />
>>    <processor class="solr.DistributedUpdateProcessorFactory"/>
>>    <processor class="solr.RunUpdateProcessorFactory" />
>>  </updateRequestProcessorChain>
>>
>>    <!-- activate RNI processing by adding the RNI URP to the chain
>> for xml updates -->
>>  <requestHandler name="/update"
>>                  class="solr.XmlUpdateRequestHandler">
>>    <lst name="defaults">
>>      <str name="update.chain">RNI</str>
>>    </lst>
>>    </requestHandler>
>
>
> --
> Markus Jelsma - CTO - Openindex
> http://www.linkedin.com/in/markus17
> 050-8536600 / 06-50258350