Uwe Schindler created SOLR-11677:
------------------------------------
Summary: Add ability to "enforce" in-place updates
Key: SOLR-11677
URL: https://issues.apache.org/jira/browse/SOLR-11677
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Components: update
Affects Versions: 6.6
Reporter: Uwe Schindler
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!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
