Re: Providing own _version field in solr doc

2015-12-23 Thread Debraj Manna
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

2015-12-23 Thread Shawn Heisey
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

2015-12-23 Thread Debraj Manna
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

2015-12-23 Thread Debraj Manna
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

2015-12-23 Thread Shawn Heisey
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

2015-12-22 Thread Debraj Manna
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

2015-12-14 Thread Debraj Manna
Can I somehow get "documentVersion" for each doc back in the Update Response like the way we get _version back in Optimistic Concurrency when we set "version=true" in the update request? On Dec 14, 2015 10:58 PM, "Chris Hostetter" wrote: > > The _version_ field used to

Re: Providing own _version field in solr doc

2015-12-14 Thread Andrea Gazzarini
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

2015-12-14 Thread Alexandre Rafalovitch
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

2015-12-14 Thread Chris Hostetter
The _version_ field used to optimistic concurrency can't be user supplied -- it's not just a record of the *document's* version, but actually a record of the *update command* version -- so even deleteByQuery commands have one -- and the order must (internally) increase across all types of