You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Gus Heck (JIRA)" <ji...@apache.org> on 2019/04/04 00:47:00 UTC
[jira] [Resolved] (SOLR-13150) Enforce a max cardinality on
category routed aliases
[ https://issues.apache.org/jira/browse/SOLR-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gus Heck resolved SOLR-13150.
-----------------------------
Resolution: Fixed
> Enforce a max cardinality on category routed aliases
> ----------------------------------------------------
>
> Key: SOLR-13150
> URL: https://issues.apache.org/jira/browse/SOLR-13150
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
> Affects Versions: master (9.0)
> Reporter: Gus Heck
> Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> This ticket will add the check to enforce a (configurable) maximum number of collections in a category routed alias. The purpose of this check is to provide a safety valve to ensure that unexpected data values don't cause run-away collection creation. This check should happen within the validateRouteValue() method specified by RoutedAlias
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org