[
https://issues.apache.org/jira/browse/SOLR-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829375#comment-16829375
]
Tomás Fernández Löbbe commented on SOLR-13320:
----------------------------------------------
Yes, it's not a new parameter, but my point is that it achieves the use case
Scott proposed. You just need to have a version field (which I don't remember
if it can be \_version\_ or if it needs to be a new version field) that could
actually be a constant number in your case, since you don't really care about
versioning AFAICT.
You could then, define an UpdateRequestProcessorChain where you use
DocBasedVersionConstraintsProcessor and use that for your backfill, knowing
that it'll skip any docs that already exist in the index.
DocBasedVersionConstraintsProcessor also has the advantage that it works with
deletes, by creating tombstones (though, in that case, you'd also have to use
the DBVCP for regular updates).
I'm not sure it's a good idea to add a new global parameter to do something
that can already be done. Also, looking at your patch, it seems to only work in
Cloud mode?
> add a param ignoreVersionConflicts=true to updates to not overwrite existing
> docs
> ---------------------------------------------------------------------------------
>
> Key: SOLR-13320
> URL: https://issues.apache.org/jira/browse/SOLR-13320
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Major
> Attachments: SOLR-13320.patch
>
>
> Updates should have an option to ignore duplicate documents and drop them if
> an option {{ignoreDuplicates=true}} is specified
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
