[
https://issues.apache.org/jira/browse/SOLR-10804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159736#comment-17159736
]
Adam Woods commented on SOLR-10804:
-----------------------------------
Hi - we are currently compiling our own DocBasedVersionConstraintsProcessor
exactly for this purpose.
We have the same use case; re-indexing without deleting documents or creating a
new collection.
* The version comes from the source data
* Our indexing process transforms the data into a new structure to meet our
search requirements in Solr.
We're in the process of upgrading to the latest version and it looks like i'll
need to re-write our own version of the processor as it seems the source has
changed in this area between versions. At the same time, I'd like to move away
from having to compile this for new versions of Solr in the future.
Are you happy to take a PR on this? If so - any opinions on the naming?
The
[documentation|https://lucene.apache.org/solr/8_6_0/solr-core/org/apache/solr/update/processor/DocBasedVersionConstraintsProcessorFactory.html]
seems to focus more on outcome of rejection; rather than overwriting. So
perhaps a name like rejectSameVersion with a default of true would keep
consistency a little more.
> Document Centric Versioning Constraints - Overwrite same version
> ----------------------------------------------------------------
>
> Key: SOLR-10804
> URL: https://issues.apache.org/jira/browse/SOLR-10804
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 6.1
> Reporter: Sergio Garcia Maroto
> Priority: Major
> Fix For: 7.0
>
>
> It would be nice to have the possibility to overwrite documents with the same
> external version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
