[
https://issues.apache.org/jira/browse/SOLR-12373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480635#comment-16480635
]
Michael Braun commented on SOLR-12373:
--------------------------------------
[~tomasflobbe] I can definitely see where this could be a problem and render
the tombstone functionality less usable. Should there maybe be additionally a
way of overriding what to do on the tombstone document, like making
createTombstoneDocument a protected instance method so if someone wants to
customize the class more they can, in the event these defaults don't work?
> DocBasedVersionConstraintsProcessor doesn't work when schema has required
> fields
> --------------------------------------------------------------------------------
>
> Key: SOLR-12373
> URL: https://issues.apache.org/jira/browse/SOLR-12373
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Tomás Fernández Löbbe
> Assignee: Tomás Fernández Löbbe
> Priority: Minor
> Attachments: SOLR-12373.patch
>
>
> DocBasedVersionConstraintsProcessor creates tombstones when processing a
> delete by id. Those tombstones only have id (or whatever the unique key name
> is) and version field(s), however, if the schema defines some required
> fields, adding the tombstone will fail.
--
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
