[
https://issues.apache.org/jira/browse/SOLR-13166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786298#comment-16786298
]
Amrit Sarkar commented on SOLR-13166:
-------------------------------------
Hi Erick,
> 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.
That is true.
> Make sure to test the Admin UI's Schema Browser functionality too. That it
> presents a good error message, and perhaps pops up a dialogue "Are you sure
> you want to add more than 1000 fields to the schema? YES / NO", whereupon
> clicking YES will add the force=true ??
Yes, I was wondering to do something like that. Popup with a message for Solr
Admin UI, make it generic for every endpoint. I will see what can I do.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
