You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/08/25 18:26:00 UTC

[jira] [Commented] (METRON-1135) Make Stellar field transformations handle nulls properly

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

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

GitHub user cestella opened a pull request:

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

    METRON-1135: Make Stellar field transformations handle nulls properly

    ## Contributor Comments
    As it stands, stellar field transformations disallow users to set variables to null (and thus remove the field). This should be corrected. For instance,
    ```
    "fieldTransformations" : [
            { "transformation" : "STELLAR"
            ,"output" : [ "new_field", "new_field2"]
            ,"config" : {
              "new_field" : "old_field"
             ,"new_field2" : "old_field2"
             ,"old_field" : "null"
             ,"old_field2" : "null"
                        }
            }
    ]
    ```
    should rename "old_field" to "new_field and "old_field2" to "old_field2" The current behavior is to keep all 4 fields and to not change old_field or old_field2 at all.
    
    Manual testing:
    * Create a sensor with the field transformation above.
    * Send data through with `old_field` set to a value
    * Ensure that `old_field` does not exist in any message in the index for your sensor and it is replaced with `new_field`.
    
    ## 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 && 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 METRON-1135

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

    https://github.com/apache/metron/pull/718.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 #718
    
----
commit 3144f5b01679313f06a222b9b54d83be8a5eca48
Author: cstella <ce...@gmail.com>
Date:   2017-08-25T18:23:42Z

    METRON-1135: Make Stellar field transformations handle nulls properly

----


> Make Stellar field transformations handle nulls properly
> --------------------------------------------------------
>
>                 Key: METRON-1135
>                 URL: https://issues.apache.org/jira/browse/METRON-1135
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Casey Stella
>
> As it stands, stellar field transformations disallow users to set variables to null (and thus remove the field).  This should be corrected.  For instance, 
> {code}
> "fieldTransformations" : [
>         { "transformation" : "STELLAR"
>         ,"output" : [ "new_field", "new_field2"]
>         ,"config" : {
>           "new_field" : "old_field"
>          ,"new_field2" : "old_field2"
>          ,"old_field" : "null"
>          ,"old_field2" : "null"
>                     }
>         }
> ]
> {code}
> should rename "old_field" to "new_field and "old_field2" to "old_field2"  The current behavior is to keep all 4 fields and to not change old_field or old_field2 at all.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)