[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488026#comment-16488026
]
ASF subversion and git services commented on SOLR-12378:
--------------------------------------------------------
Commit 48bd259516b8d78c991239fe7cf3340c90f582e5 in lucene-solr's branch
refs/heads/master from markrmiller
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=48bd259 ]
SOLR-12378: Support missing versionField on indexed docs in
DocBasedVersionConstraintsURP.
> Support missing versionField on indexed docs in DocBasedVersionConstraintsURP
> -----------------------------------------------------------------------------
>
> Key: SOLR-12378
> URL: https://issues.apache.org/jira/browse/SOLR-12378
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
> Affects Versions: master (8.0)
> Reporter: Oliver Bates
> Assignee: Mark Miller
> Priority: Minor
> Labels: features, patch
> Attachments: SOLR-12378.patch, SOLR-12378.patch,
> supportMissingVersionOnOldDocs-v1.patch
>
>
> -If we want to start using DocBasedVersionConstraintsUpdateRequestProcessor
> on an existing index, we have to reindex everything to set value for the
> 'versionField' field, otherwise- We can't start using
> DocBasedVersionConstraintsUpdateRequestProcessor on an existing index because
> we get this line throwing shade:
> {code:java}
> throw new SolrException(SERVER_ERROR,
> "Doc exists in index, but has null versionField: "
> + versionFieldName);
> {code}
> We have to reindex everything into a new collection, which isn't always
> practical/possible. The proposal here is to have an option to allow the
> existing docs to be missing this field and to simply treat those docs as
> older than anything coming in with that field set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
