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

Erick Erickson commented on SOLR-13166:
---------------------------------------

Amrit:

I did a very quick scan and want to verify one thing. For something like 
changing docvalues from false to true, there's the 
UninvertDocValuesMergePolicyFactory, which _does_ (under special circumstances) 
allow you to change docValues.

It looks like we can override the checks with the "force" option, in which case 
things are fine. Is that true? I like the idea that in that expert case they 
need to do "other stuff" _before_ making the change, so this is great.

> Add smart checks for Config and Schema API in Solr to avoid malicious updates
> -----------------------------------------------------------------------------
>
>                 Key: SOLR-13166
>                 URL: https://issues.apache.org/jira/browse/SOLR-13166
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: config-api, Schema and Analysis
>            Reporter: Amrit Sarkar
>            Priority: Major
>         Attachments: SOLR-13166.patch, SOLR-13166.patch, SOLR-13166.patch
>
>
> While working with Solr, schema and configuration changes without 
> understanding can result in severe node failures, and much effort and time 
> get consumed to fix such situations.
> Few such problematic situations can be:
> * Too many fields in the schema
> * Too many commits: too short auto commit
> * Spellchecker, suggester issues. Build suggester index on startup or on 
> every commit causes memory pressure and latency issues
> -- Schema mess-ups
> * Text field commented out and Solr refuses to reload core
> * Rename field type for unique key or version field
> * Single-valued to multivalued and vice versa
> * Switching between docvalues on/off
> * Changing text to string type because user wanted to facet on a text field
> The intention is to add a layer above Schema and Config API to have some 
> checks and let the end user know the ramifications of the changes he/she 
> intends to do.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to