Can you elaborate on bulk or streaming API’s?
Mark Miller-3 wrote
> As long as you are not using the bulk or streaming API’s. Solrj does not
> currently respect delete/add ordering in those cases, though each of the
> two types are ordered. For the standard update per request, as long as
> it’s
As long as you are not using the bulk or streaming API’s. Solrj does not
currently respect delete/add ordering in those cases, though each of the two
types are ordered. For the standard update per request, as long as it’s the
same client, this is a guarantee.
- Mark
On Dec 17, 2013, at 9:54 AM
Yes, SolrCloud uses a transaction log to keep track of ordered updates to a
document. The latest update will be immediately visible from the real-time get
handler /get?id=X even without a commit.
Cheers,
Timothy Potter
Sr. Software Engineer, LucidWorks
www.lucidworks.com
___
This link has a good description of Solr's optimistic locking feature:
http://yonik.com/solr/optimistic-concurrency/
This is designed for READ-MODIFY-WRITE operations. This will guarantee
that you are updating the same version of the document that you read. The
full delete of the document though
