field that counts how many we have tried to insert the same
> query. We are using Solr 3.6, so how can we use (from the code of our custom
> update handler) the deduplicatin request processor to check if the query we
> are trying to insert/update already exists?
>
> Greetings!
&
are using Solr 3.6, so how can we use (from the code of our custom update
handler) the deduplicatin request processor to check if the query we are trying
to insert/update already exists?
Greetings!
___
Further progress now hampered by configuring an update log. When I
follow instructions found around the web, I get this:
SEVERE: Unable to create core: collection1
caused by
Caused by: java.lang.NullPointerException
at
org.apache.solr.common.params.SolrParams.toSolrParams(SolrParams.java:
Many thanks.
Let me record here what I have tried.
I have viewed:
http://wiki.apache.org/solr/UpdateXmlMessages
and this github project which is suggestive:
https://github.com/industria/solrprocessors
I now have two UpdateRequestChains:
hello
and the new
You need to refer to your chain in a RequestHandler config. Search for
/update, duplicate that, and change the chain it points to.
Upayavira
On Mon, Mar 11, 2013, at 05:22 AM, Jack Park wrote:
> With 4.1, not in cloud configuration, I have a custom response handler
> chain which injects an additi
With 4.1, not in cloud configuration, I have a custom response handler
chain which injects an additional handler for studying the documents
as they come in. But, when I do partial updates on those documents, I
don't want them to be studied again, so I created another version of
the same chain, but
Hi:
I'm trying to build a custom update handler to accomplish one specific task. In
our app we do query suggestions based on previous queries passed into our
frontend app, the thing is that instead of getting this queries from the solr
logs, we stored in a separated core. So far so good
