[
https://issues.apache.org/jira/browse/LUCENE-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887208#comment-16887208
]
ASF subversion and git services commented on LUCENE-8316:
---------------------------------------------------------
Commit 1ecd02deb504f27d602fdac83862a50e896c2dc6 in lucene-solr's branch
refs/heads/master from Munendra S N
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=1ecd02d ]
SOLR-12368: inplace update for field that doesn't yet exist in any doc
If the field is non-stored, non-indexed and docvalue enabled numeric field
then inplace update can be done. previously, lucene didn't support
docvalue update for field that is not yet present in indexWriter but
LUCENE-8316 added support for this.
This adds support to update field which satisfies inplace conditions
but which doesn't yet exist in any docs
> Allow DV updates for not existing fields
> ----------------------------------------
>
> Key: LUCENE-8316
> URL: https://issues.apache.org/jira/browse/LUCENE-8316
> Project: Lucene - Core
> Issue Type: Improvement
> Affects Versions: 7.4, 8.0
> Reporter: Simon Willnauer
> Priority: Major
> Fix For: 7.4, 8.0
>
> Attachments: LUCENE-8316.patch, LUCENE-8316.patch
>
>
> Today we prevent DV updates for non-existing fields except
> of the soft deletes case. Yet, this can cause inconsitent field numbers
> etc. since we don't go through the global field number map etc. This
> change removes the limitation of updating DVs in docs even if the field
> doesn't exists. This also has the benefit that the error messages if
> the field type doesn't match is consistent with what DWPT throws.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
