[SOLR-12368] in-place DV updates should no longer have to jump through hoops if field does not yet exist

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Done
• Fix Version/s: 8.3
• Assignee: Munendra S N
• Reporter: Chris M. Hostetter
• Created: 16/May/18 22:40
• Updated: 29/Oct/19 16:35
• Resolved: 17/Jul/19 16:29

Description

When SOLR-5944 first added "in-place" DocValue updates to Solr, one of the edge cases thta had to be dealt with was the limitation imposed by IndexWriter that docValues could only be updated if they already existed - if a shard did not yet have a document w/a value in the field where the update was attempted, we would get an error.

LUCENE-8316 seems to have removed this error, which i believe means we can simplify & speed up some of the checks in Solr, and support this situation as well, rather then falling back on full "read stored fields & reindex" atomic update

Issue Links

• blocks: LUCENE-8909 Deprecate getFieldNames from IndexWriter
• is related to: SOLR-11286 First doc Inplace Update, updating whole document.
• is related to: LUCENE-7659 IndexWriter should expose field names
• relates to: SOLR-5944 Support updates of numeric DocValues
• relates to: LUCENE-8316 Allow DV updates for not existing fields