Re: AW: Howto verify that update is "in-place"

2017-10-18 Thread alessandro.benedetti
According to the concept of immutability that should drive Lucene segmenting approach, I think Emir observation sounds correct. Being docValues a column based data structure, stored on segments i guess when an in place update happens it does just a re-index of just that field. This means we need

Re: AW: Howto verify that update is "in-place"

2017-10-18 Thread Emir Arnautović
gain 70ms. So I assume that my operation did re-index the > whole document and was thus not an in-place update. > > > -Ursprüngliche Nachricht- > Von: Amrit Sarkar [mailto:sarkaramr...@gmail.com] > Gesendet: Dienstag, 17. Oktober 2017 12:43 > An: solr-user@lucene.apache.org &

AW: Howto verify that update is "in-place"

2017-10-17 Thread James
enstag, 17. Oktober 2017 12:43 An: solr-user@lucene.apache.org Betreff: Re: Howto verify that update is "in-place" James, @Amrit: Are you saying that the _version_ field should not change when > performing an atomic update operation? It should change. a new version will be allotte

AW: Howto verify that update is "in-place"

2017-10-17 Thread Julian Ohrt
not change when performing an atomic update operation? Thanks James -Ursprüngliche Nachricht- Von: Amrit Sarkar [mailto:sarkaramr...@gmail.com] Gesendet: Dienstag, 17. Oktober 2017 11:35 An: solr-user@lucene.apache.org Betreff: Re: Howto verify that update is "in-place"

Re: Howto verify that update is "in-place"

2017-10-17 Thread Amrit Sarkar
orming an atomic update operation? > > Thanks > James > > > -Ursprüngliche Nachricht- > Von: Amrit Sarkar [mailto:sarkaramr...@gmail.com] > Gesendet: Dienstag, 17. Oktober 2017 11:35 > An: solr-user@lucene.apache.org > Betreff: Re: Howto verify that update is "in-

AW: Howto verify that update is "in-place"

2017-10-17 Thread James
that the _version_ field should not change when performing an atomic update operation? Thanks James -Ursprüngliche Nachricht- Von: Amrit Sarkar [mailto:sarkaramr...@gmail.com] Gesendet: Dienstag, 17. Oktober 2017 11:35 An: solr-user@lucene.apache.org Betreff: Re: Howto verify that update

Re: Howto verify that update is "in-place"

2017-10-17 Thread Amrit Sarkar
Hi James, As for each update you are doing via atomic operation contains the "id" / "uniqueKey". Comparing the "_version_" field value for one of them would be fine for a batch. Rest, Emir has list them out. Amrit Sarkar Search Engineer Lucidworks, Inc. 415-589-9269 www.lucidworks.com Twitter

Re: Howto verify that update is "in-place"

2017-10-17 Thread Emir Arnautović
Hi James, I did not try, but checking max and num doc might give you info if update was in-place or atomic - atomic is reindexing of existing doc so the old doc will be deleted. In-place update should just update doc values of existing doc so number of deleted docs should not change. HTH, Emir

Howto verify that update is "in-place"

2017-10-17 Thread James
I am using Solr 6.6 and carefully read the documentation about atomic and in-place updates. I am pretty sure that everything is set up as it should. But how can I make certain that a simple update command actually performs an in-place update without internally re-indexing all other fields?