[SOLR-11677] Add ability to "enforce" in-place updates

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 6.6
• Component/s: update
• Assignee: Unassigned
• Reporter: Uwe Schindler
• Created: 27/Nov/17 10:16
• Updated: 08/Jun/19 15:16

Description

There is currently a problem with in-place updates: Under certain conditions, an in-place update does not work, so Solr internally reindexes the whole document. This is not bad in most cases, unless you have some fields in your documents that are not stored (e.g. large fulltext fields). In that case, the try to do in-place update leads to data loss!

I'd suggest to add a request parameter in the update to "enforce in-place mode". If not all conditions are met (e.g. field configuration is incompatible, version field does not have all required settings, or user uses other operations than "add" or "increment"), the request should simply fail - to prevent data loss!

There is also a related issue that may lead to data loss because of the same issue: SOLR-11286. In this case it is completely unexpected because everything is correct from the schema settings, but it still does reindex.

So there should really be a way to enforce in-place docvalues updates and fail otherwise!

Another thing to maybe think of: Only prevent "reindexing" updates if documents have some fields that are unstored!

Issue Links

• is broken by: SOLR-11286 First doc Inplace Update, updating whole document.