lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Gazzarini <>
Subject Re: UpdateProcessor not working with DIH, but works with SolrJ
Date Thu, 22 Aug 2013 16:06:34 GMT
yes, yes of course, you should use your already declared request 
handler...that was just a copied and pasted example :)

I'm curious about what kind of error you got....I copied the snippet 
above from a working core (just replaced the name of the chain)

BTW: AFAIK is the "update.processor" that has been deprecated in favor 
of "update.chain" so this shouldn't be the problem.


On 08/22/2013 05:57 PM, Shawn Heisey wrote:
> On 8/22/2013 9:42 AM, Andrea Gazzarini wrote:
>> You should declare this
>> <str name="update.chain">nohtml</str>
>> in the "defaults" section of the RequestHandler that corresponds to your
>> dataimporthandler. You should have something like this:
>>      <requestHandler name="/dataimport"
>> class="org.apache.solr.handler.dataimport.DataImportHandler">
>>          <lst name="defaults">
>>              <str name="config">dih-config.xml</str>
>>              <str name="update.chain">nohtml/str>
>>          </lst>
>>      </requestHandler>
>> Otherwise the default update chain will be called (and your URP are not
>> part of that). The solrj, behind the scenes, is a client of the /update
>> request handler, that's the reason why using that you can see your URP
>> working.
> This results in an error parsing the config, so my cores won't start 
> up.  I saw another message via google that talked about using 
> update.processor instead of update.chain, so I tried that as well, 
> with no luck.
> Can I ask DIH to use the /update handler that I have declared already?
> Thanks,
> Shawn

View raw message