lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Sebastien Vachon <>
Subject RE: Update single field through SolrJ
Date Tue, 01 Apr 2014 15:09:47 GMT

Thanks for pointing me in the proper direction. I managed to change my code to send atomic
updates through SolrJ but this morning we experienced something weird. I sent a large batch
of updates and deletes through SolrJ and our Cloud quickly became unusable and unresponsive
(no leader for a shard, etc).

We looked through the logs and could not find a particular reason for this. We waited quite
some time but some nodes were not showing any progress in their recovery so we restarted them
(we are running Tomcat 7.0.39) and everything came back as if nothing happened.

Does anyone experienced something similar? We are currently running Solr 4.6.1 on a 5 nodes
cluster with both ZK 3.4.5 and Solr on them (ZK has its own storage device to minimize the
impact). Both are also running under JRE 1.7.0_21 in 64 bits mode. Our index has 5 shards
with 2 replicas.

Thanks for your help

> -----Original Message-----
> From: Shawn Heisey []
> Sent: March-28-14 3:21 PM
> To:
> Subject: Re: Update single field through SolrJ
> On 3/28/2014 1:02 PM, Jean-Sebastien Vachon wrote:
> > I`d like to know how (it is possible) to update a field`s value using SolrJ. I
> looked at the API and could not figure it out so for now I'm using the
> UpdateHandler by sending it a JSON formatted document illustrating the
> required changes.
> >
> >
> > Is there a way to do the same through SolrJ?
> The feature you are after is called Atomic Updates.  In order to use this
> feature *all* of your fields must be stored, except for copyField destinations.
> See especially the "Caveats and Limitations" section of the first link below:
> ments
> To do this with SolrJ, you must use a Map for the field value instead of just
> one or more regular values:
> field-update-modes-atomic-updates-with-solrj
> Thanks,
> Shawn
> -----
> Aucun virus trouvé dans ce message.
> Analyse effectuée par AVG -
> Version: 2014.0.4354 / Base de données virale: 3722/7256 - Date:
> 27/03/2014

View raw message