[
https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525194#comment-16525194
]
ASF GitHub Bot commented on METRON-1643:
----------------------------------------
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/1083#discussion_r198536558
--- 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 --
I don't take it as an indictment on match, but more on stellar and the
requirement for a meta programming mode through the transformation construct.
So... don't be so tough on yourself.
> 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)
