Re: docvalues set to true, and indexed is false and stored is set to false

Hi Ganesh, I cannot confirm for sure, but I would assume that it will not get reindexed, but just segments doc values file rewritten. It is best if you test this and see for yourself. Regards, Emir -- Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Supp

Re: docvalues set to true, and indexed is false and stored is set to false

Hi Emir, Thanks for confirming that strField is not considered / available for in place updates. As per documentation, it says... *An atomic update operation is performed using this approach only when the fields to be updated meet these three conditions: are non-indexed (indexed="false"), non-

Re: docvalues set to true, and indexed is false and stored is set to false

Hi Ganesh, Doc values are enabled for strField and UUID but in place updates are not. It is not free = according to some discussions on mailing list (did not check the code) in place updates are not update of some value in doc values file but rewrite of doc values file for the segment that it is

Re: docvalues set to true, and indexed is false and stored is set to false

Hi, Thanks for clearing. But as per this link (Enabling DocValues) it says that it supports strField and UUID field also. Again, what you mean by it's not free for large segments. Can you point me to some d

Re: docvalues set to true, and indexed is false and stored is set to false

Hi, It is clearer now, but you mentioned strings in your first mail and in place updates only work for numeric fields. If you meet all conditions, document will not be reindexed, but only doc values rewritten for the segment where in place update happened. Note that this is not free for large se

Re: docvalues set to true, and indexed is false and stored is set to false

Hi, I guess my point is not conceived correctly. Here I am talking about the field "In Place Updates " As per above link, it says that complete document will not be re-indexed

Re: docvalues set to true, and indexed is false and stored is set to false

Whenever you send doc to indexing, it is indexed completely and old document with the same id (if one exists) is just flagged as deleted and will be removed from index when segment that it is stored is merged. In case of large segments, it might be never. The safest option is to do full reindex

Re: docvalues set to true, and indexed is false and stored is set to false

Hi, Thanks for quick response. I forgot to mention that after adding it, I have re-indexed all the data with dynamic fields Field_one, Field_two etc. In that case, by adding new field ( docvalue field ) or removing existing docvalue field, Will the whole document will re-indexed again, or only

Re: docvalues set to true, and indexed is false and stored is set to false

Hi, Changing schema will not do anything by itself. After changes are applied (core reloaded if not used API to update schema) it will use new schema to index new documents. What matters is what you had in index before schema updates. So if you had defined Field_one as string or you had it as nu