[
https://issues.apache.org/jira/browse/SOLR-13527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshum Gupta updated SOLR-13527:
--------------------------------
Summary: Control update requests based on usage (was: Control access to
update requests based on usage)
> Control update requests based on usage
> --------------------------------------
>
> Key: SOLR-13527
> URL: https://issues.apache.org/jira/browse/SOLR-13527
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Anshum Gupta
> Assignee: Anshum Gupta
> Priority: Major
>
> Solr is open ended by design, and while that works for use cases where the
> owner and user of the Solr cluster are the same set of people, it quickly
> gets unmanageable when that’s not the case. As an example, there is no
> restriction on the core size or the number of fields that can be defined.
> It would be very useful to have an extendible way to be able to control and
> limit the way Solr is used from a platform perspective. Not only would the
> owner of Solr cluster/service be happy this way, the users would also get a
> much better uptime.
> This is an umbrella JIRA for a framework that allows for controlling access
> to Solr based on usage e.g.: core size, number of fields
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
