[
https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534972#comment-16534972
]
ASF GitHub Bot commented on METRON-1643:
----------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1083
" Ultimately, I consider this a stop-gap."
Yes. What we are basically doing is writing a meta language on top of
stellar. In this case we are using that to make up for the meta language
itself not supporting multi-line input ( and stellar's support for that as well
)
A question would be, why would this transform not just be transformed into
a match statement instead of adding a new function?
How much of this pain is from not using the UI for editing? Would a ui
editor that let you put in a multi line match make this pain better?
> 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)
