r logs lines, but if i remember
> > > correctly, you must put all custom processors above Log, Distributed
> and
> > > Run, at least i remember i read it somewhere a long time ago.
> > > >
> > > > We put all our custom processors on top of the three default
&g
ove Log, Distributed and
> > Run, at least i remember i read it somewhere a long time ago.
> > >
> > > We put all our custom processors on top of the three default processors
> > and they run just fine.
> > >
> > > Try it.
> > >
> > > Reg
>
> > Try it.
> >
> > Regards,
> > Markus
> >
> > -----Original message-
> > > From:Rahul Goswami
> > > Sent: Wednesday 18th September 2019 22:20
> > > To: solr-user@lucene.apache.org
> > > Subject: Custom update process
ors and
> they run just fine.
>
> Try it.
>
> Regards,
> Markus
>
> -Original message-
> > From:Rahul Goswami
> > Sent: Wednesday 18th September 2019 22:20
> > To: solr-user@lucene.apache.org
> > Subject: Custom update processor not kic
essors and
they run just fine.
Try it.
Regards,
Markus
-Original message-
> From:Rahul Goswami
> Sent: Wednesday 18th September 2019 22:20
> To: solr-user@lucene.apache.org
> Subject: Custom update processor not kicking in
>
> Hello,
>
> I am using solr 7.2.1
Hello,
I am using solr 7.2.1 in a standalone mode. I created a custom update
request processor and placed it between the distributed processor and run
update processor in my chain. I made sure the chain is invoked since I see
log lines from the getInstance() method of my processor factory. But I
d
