[
https://issues.apache.org/jira/browse/SOLR-13151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772169#comment-16772169
]
Gus Heck commented on SOLR-13151:
---------------------------------
My thought was to perform this as part of validateRouteValue(). At some point
we might want add an overflow collection to handle maxCardinality excess in a
more tolerant fashion until the situation can be evaluated by a human, but
probably we still want to complain about unexpected values in that case.
> Provide regex based category validation for CategoryRoutedAliases
> -----------------------------------------------------------------
>
> Key: SOLR-13151
> URL: https://issues.apache.org/jira/browse/SOLR-13151
> 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
>
> This ticket will add the check to enforce a (configurable, optional) regular
> expression to enreject requests that attempt to add an unexpected category,
> or a malformed category to a category routed alias. The purpose of this check
> is to provide a safety valve to ensure that unexpected data values don't
> cause creation of collections inconsistent with the user's intended design.
> 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: [email protected]
For additional commands, e-mail: [email protected]
