[jira] [Commented] (METRON-1643) Create a REGEX_ROUTING field transformation

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/METRON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525154#comment-16525154 ] 

ASF GitHub Bot commented on METRON-1643:
----------------------------------------

GitHub user cestella opened a pull request:

    https://github.com/apache/metron/pull/1083

    METRON-1643: Create a REGEX_ROUTING field transformation

    ## Contributor Comments
    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.
    
    
    ## Pull Request Checklist
    
    Thank you for submitting a contribution to Apache Metron.  
    Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions.  
    Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides.  
    
    
    In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
    - [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    
    ### For code changes:
    - [x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
    - [x] Have you included steps or a guide to how the change may be verified and tested manually?
    - [x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
      ```
      mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh 
      ```
    
    - [x] Have you written or updated unit tests and or integration tests to verify your changes?
    - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
    - [x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?
    
    ### For documentation related changes:
    - [x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`:
    
      ```
      cd site-book
      mvn site
      ```
    
    #### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
    It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cestella/incubator-metron regex_routing

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metron/pull/1083.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1083
    
----
commit 5030d00f9eb13ff662716f1c05a731938a66cb52
Author: cstella <ce...@...>
Date:   2018-06-05T19:05:59Z

    Regex based message router transformer.

commit 7c2723bc243996a2a0606e07def5e3b5c1736e59
Author: cstella <ce...@...>
Date:   2018-06-06T14:35:25Z

    updating test

commit 4a5461a8a7b4cd34d6541c0449470901d6ef3ed5
Author: cstella <ce...@...>
Date:   2018-06-08T02:56:50Z

    Merge branch 'master' into regex_routing

commit f1bda7478824e716d60a28cab8680e303a9e28a7
Author: cstella <ce...@...>
Date:   2018-06-08T03:03:34Z

    regex routing docs

commit ba862789e43f9e5d8e648d86378d89ec98d30d5b
Author: cstella <ce...@...>
Date:   2018-06-27T14:19:42Z

    Merge branch 'master' into regex_routing

----


> 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)