[ https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525183#comment-16525183 ]
ASF GitHub Bot commented on METRON-1643: ---------------------------------------- Github user cestella commented on a diff in the pull request: https://github.com/apache/metron/pull/1083#discussion_r198530993 --- Diff: metron-platform/metron-parsers/README.md --- @@ -337,6 +337,28 @@ The following config will rename the fields `old_field` and `different_old_field ] } ``` +* `REGEX_ROUTING` : This transformation lets users set an output field to one of a set of possibilities based on matching regexes. This has functional overlap with Stellar match statements, but the syntax is more bearable for large sets of conditionals. --- End diff -- Yeah, that was wrong of me. I had a bad night, when I wrote that. My bad. Will correct right away. `match` is and continues to be awesome. :) > 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)