[SOLR-13150] Enforce a max cardinality on category routed aliases

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 9.0
• Component/s: UpdateRequestProcessors
• Assignee: Unassigned
• Reporter: Gus Heck
• Created: 20/Jan/19 22:03
• Updated: 04/Apr/19 00:46
• Resolved: 04/Apr/19 00:46

Description

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

Issue Links

• links to: GitHub Pull Request #573