[
https://issues.apache.org/jira/browse/SOLR-13151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772784#comment-16772784
]
mosh commented on SOLR-13151:
-----------------------------
As I made progress working on this ticket as well as SOLR-13150,
It has dawned upon me that no metadata validation is done during the
CreateAlias command.
I was thinking whether a RoutedAlias#validate method could be added,
and be called inside CreateAliasCmd#callCreateRoutedAlias.
I have contemplated whether the validation should be done in the RoutedAlias'
constructor,
though this might add unneeded overhead, since the constructor is used when the
alias is accessed and not only during the alias' initial creation.
{color}
> 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]
