Re: Atomic updates and stored CopyTo destination fields

On 11/14/2018 10:35 AM, Jon Kjær Amundsen wrote: It is not that I want it. I just can't reproduce it even though I read it as an expected behaviour. So I wondered if something has been changed since the warning was written, or if I had misunderstood something. To my knowledge, nothing has chan

Re: Atomic updates and stored CopyTo destination fields

It is not that I want it. I just can't reproduce it even though I read it as an expected behaviour. So I wondered if something has been changed since the warning was written, or if I had misunderstood something. ons. d. 14. nov. 2018 17.09 skrev Erick Erickson : > I'm a little confused on what y

Re: Atomic updates and stored CopyTo destination fields

I'm a little confused on what you're trying. Say your source field is Y and your destination field X. Are you saying that you want your destination field X to contain both the old value of field Y and the new value of field Y when you atomically update that field Y? H, I'm actually not sure wh

Atomic updates and stored CopyTo destination fields

Reading up on atomic updates, the Solr reference guide states the following: The core functionality of atomically updating a document requires that all fields in your schema must be configured as stored (stored="true") or docValues (docValues="true") except for fields which are destinations, whic

Re: Atomic updates and "stored"

Thanks Eric! Best, Mark On Mon, May 23, 2016 at 1:35 PM, Erick Erickson wrote: > Yes, currently when using Atomic updates _all_ fields > have to be stored, except the _destinations_ of copyField > directives. > > Yes, it will make your index bigger. The affects on speed are > probably minimal t

Re: Atomic updates and "stored"

Yes, currently when using Atomic updates _all_ fields have to be stored, except the _destinations_ of copyField directives. Yes, it will make your index bigger. The affects on speed are probably minimal though. The stored data is in your *.fdt and *.fdx segments files and are not referenced only t

Atomic updates and "stored"

Hi, I have some 150 fields in my schema out of which about 100 are dynamic fields which I am not storing (stored="false"). In case I need to do an atomic update to one or two fields which belong to the stored list of fields, do I need to change my dynamic fields (100 or so now not "stored") to sto