Re: Providing own _version field in solr doc

For my use case I tried document centric versioning as mentioned here . But In my case this is not working I am seeing the document having version older is

Re: Providing own _version field in solr doc

On 12/23/2015 10:30 AM, Debraj Manna wrote: > For my use case I tried document centric versioning as mentioned here > . > But In my case this is not working I

Re: Providing own _version field in solr doc

Thanks Shawn. But after making the below changes (making versionable_chain as default) all my update,inserts & deleteByQuery are failing with the error "*Error from server at http://localhost:/solr/discovery : DistributedUpdateProcessor must follow

Re: Providing own _version field in solr doc

Thanks Shawn :) . On Dec 24, 2015 1:12 AM, "Shawn Heisey" wrote: > On 12/23/2015 12:25 PM, Debraj Manna wrote: > > Thanks Shawn. But after making the below changes (making > versionable_chain > > as default) all my update,inserts & deleteByQuery are failing with the > >

Re: Providing own _version field in solr doc

On 12/23/2015 12:25 PM, Debraj Manna wrote: > Thanks Shawn. But after making the below changes (making versionable_chain > as default) all my update,inserts & deleteByQuery are failing with the > error "*Error from server at http://localhost:/solr/discovery >

Re: Providing own _version field in solr doc

Hi Alex, Can you let us know what do you mean by *"timestamps" are truly atomic and not local clock-based." ?* *Thanks,* On Mon, Dec 14, 2015 at 10:53 PM, Alexandre Rafalovitch wrote: > At the first glance, this sounds like a perfect match to > >

Re: Providing own _version field in solr doc

4 Dec 2015 22:47:43 +0530 > : From: Debraj Manna <subharaj.ma...@gmail.com> > : Reply-To: solr-user@lucene.apache.org > : To: solr-user@lucene.apache.org > : Subject: Providing own _version field in solr doc > : > : We have a use case in which there are multiple clients writing &g

Providing own _version field in solr doc

We have a use case in which there are multiple clients writing concurrently to solr. Each of the doc is having an 'timestamp' field which indicates when these docs were generated. We also have to ensure that any old doc doesn't overwrite any new doc in solr. So to achieve this we were thinking if

Re: Providing own _version field in solr doc

Hi Debraj, I think this nice article [1] from Yonik could be helpful. Andrea [1] http://yonik.com/solr/optimistic-concurrency/ 2015-12-14 18:17 GMT+01:00 Debraj Manna : > We have a use case in which there are multiple clients writing concurrently > to solr. Each of

Re: Providing own _version field in solr doc

At the first glance, this sounds like a perfect match to https://cwiki.apache.org/confluence/display/solr/Updating+Parts+of+Documents#UpdatingPartsofDocuments-DocumentCentricVersioningConstraints Just make sure your "timestamps" are truly atomic and not local clock-based. The drift could cause

Re: Providing own _version field in solr doc

r-user@lucene.apache.org : To: solr-user@lucene.apache.org : Subject: Providing own _version field in solr doc : : We have a use case in which there are multiple clients writing concurrently : to solr. Each of the doc is having an 'timestamp' field which indicates : when these docs were generated. :