[
https://issues.apache.org/jira/browse/SOLR-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833460#comment-16833460
]
Yonik Seeley commented on SOLR-13320:
-------------------------------------
Hmmm, when I read "ignoreVersionConflicts" I assumed the wrong behavior... go
ahead and add even if there is a version conflict. We aren't really ignoring
it, but rather continuing on to the next update/doc in the batch after it
happened?
I'm not sure if I can think if a better name though... thinking along the lines
of [~gus_heck],
maybe something like "continueOnVersionConflict" (or "continueOnError" for the
general case)?
> 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, 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
