[jira] [Commented] (SOLR-9349) Schema API should never delete fields used elsewhere in the schema

["Shawn Heisey (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-9349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396135#comment-15396135 ] 

Shawn Heisey commented on SOLR-9349:
------------------------------------

There are some other problem situations that would be very difficult to detect -- such as deleting a field that is used for "df" or "qf" in a request handler definition.  That particular problem doesn't prevent a core from starting, but it does break queries.


> Schema API should never delete fields used elsewhere in the schema
> ------------------------------------------------------------------
>
>                 Key: SOLR-9349
>                 URL: https://issues.apache.org/jira/browse/SOLR-9349
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Schema and Analysis
>    Affects Versions: 6.1
>            Reporter: Shawn Heisey
>
> The Schema API should refuse to delete a field if it can detect that the deletion would cause the schema to fail to load.
> This includes the field assigned to uniqueKey, fields used as copyField sources, and fields used as copyField destinations.  There may be other detectable problems that haven't been listed here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org