[
https://issues.apache.org/jira/browse/LUCENE-8335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495109#comment-16495109
]
Robert Muir commented on LUCENE-8335:
-------------------------------------
Mike, I think nearly all of your same arguments could be made for preventing
the change of an IntPoint field to a FloatPoint. But as it is now, any "schema"
stuff in lucene is so minimum that, it doesn't know the difference. In the past
the reasoning has been to keep it minimal and leave that to the consuming app.
I don't think it makes sense that it can only track expert usecases.
> Do not allow changing soft-deletes field
> ----------------------------------------
>
> Key: LUCENE-8335
> URL: https://issues.apache.org/jira/browse/LUCENE-8335
> Project: Lucene - Core
> Issue Type: Improvement
> Affects Versions: 7.4, master (8.0)
> Reporter: Nhat Nguyen
> Assignee: Simon Willnauer
> Priority: Minor
> Attachments: LUCENE-8335.patch
>
>
> Today we do not enforce an index to use a single soft-deletes field. A user
> can create an index with one soft-deletes field then open an IW with another
> field or add an index with a different soft-deletes field. This should not be
> allowed and reported the error to users as soon as possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
