You can define any number of the handler end-point definitions. Also, you can pass the update chain name as part of the URL parameters. So, it could be different for each call if you want.
Regards, Alex. ---- Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter: http://www.solr-start.com/ On 7 September 2015 at 12:42, Vivek Pathak <vpat...@orgmeta.com> wrote: > Yes, i figured that out looking at solr code. > > It was a thin wrapper adding a default encoding hint, so it can be replaced > transparently by UpdateRequestHandler. > > I was interested in having a second update chain for testing duplicates, > and it had to consume json. > > Thanks > > > > On 09/07/2015 06:21 AM, Upayavira wrote: >> >> >> On Mon, Sep 7, 2015, at 11:11 AM, Vivek Pathak wrote: >>> >>> Hello, >>> >>> Wring a custom handler, I am having trouble with >>> JsonUpdateRequestHandler - getting a class not found error. >>> >>> I see web examples till 4.7. Has it been depractaed in 5.2 and what >>> class may replace it? >> >> Since 4.0, the default UpdateRequestHandler will detect the content type >> and act accordingly. >> >> What do you want your UpdateRequestHandler to do? >> >> If you want to parse your own data format, I believe you can implement >> your own ContentStreamLoader. >> >> Upayavira > >
