[
https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535025#comment-16535025
]
ASF GitHub Bot commented on METRON-1643:
----------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1083
I think a decent UI that would make this a hell of a lot easier, but also
not embedding stellar in JSON would help a lot. Something like:
```
match {
REGEXP_MATCH(pix_type, '^6-302.*') => 'cisco-6-302',
REGEXP_MATCH(pix_type, '^5-304.*') => 'cisco-5-304',
default => NULL
}
```
is a lot easier to read and deal with. Also, enabling REGEXP_MATCH to take
multiple regexes via a list in the 2nd arg would make things easier.
> Create a REGEX_ROUTING field transformation
> -------------------------------------------
>
> Key: METRON-1643
> URL: https://issues.apache.org/jira/browse/METRON-1643
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
> Priority: Major
>
> A relatively common pattern is to choose the value of a field based on if
> another field matches a set of regexes. This can be done via stellar with
> match, but if the list of possible regexes are large, that can be unwieldy.
> To ease that burden, we should have a REGEX_ROUTING field transformation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
