[
https://issues.apache.org/jira/browse/SOLR-12378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Bates updated SOLR-12378:
--------------------------------
Description:
-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.
was:
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 get this line throwing shade:
{code:java}
throw new SolrException(SERVER_ERROR,
"Doc exists in index, but has null versionField: "
+ versionFieldName);
{code}
Reindexing 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.
> 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
> Priority: Minor
> Labels: features, patch
> Attachments: 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]
