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

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

GitHub user cestella opened a pull request:

    https://github.com/apache/incubator-metron/pull/333

    METRON-249: Field Transformation functions fail to handle invalid user 
inputs

    The field transformation functions fail to handle invalid user input in a 
way that is apparent to the user what went on.  As discussed in the dev-list 
discussion, a better error message with the actual stellar statement at fault 
should be displayed rather than an opaque, general purpose antlr exception.

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

    $ git pull https://github.com/cestella/incubator-metron METRON-249-2

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

    https://github.com/apache/incubator-metron/pull/333.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 #333
    
----
commit 64f6eaba91f3179de4eae7dda1eaaba9cd994afd
Author: cstella <[email protected]>
Date:   2016-10-31T18:47:15Z

    METRON-249: Field Transformation functions fail to handle invalid user 
inputs

commit dade107e142234e503528140f5dd22d329c4322c
Author: cstella <[email protected]>
Date:   2016-10-31T18:48:04Z

    Merge branch 'master' into METRON-249-2

----


> Field Transformation functions fail to handle invalid user inputs 
> ------------------------------------------------------------------
>
>                 Key: METRON-249
>                 URL: https://issues.apache.org/jira/browse/METRON-249
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Neha Sinha
>            Priority: Minor
>              Labels: platform
>             Fix For: 0.2.1BETA
>
>         Attachments: LogException.rtf
>
>
> Hi,
> The field transformation functions fail to handle invalid user input .On 
> providing invalid inputs the parser throws exceptions and fails to create the 
> required indices in elasticsearch.
> ==========================
> Steps to Reproduce
> ==========================
> Edit the squid.json file and provide the following definition to it:-(Note-we 
> are giving an invalid input :-123 to the URL_TO_HOST function)
> -----------------------------------------------------------------------------------------------
> {
>   "parserClassName": "org.apache.metron.parsers.GrokParser",
>   "sensorTopic": "squid",
>   "parserConfig": {
>     "grokPath": "/patterns/squid",
>     "patternLabel": "SQUID_DELIMITED",
>     "timestampField": "timestamp"
>   },
>   "fieldTransformations" : [
>     {
>       "transformation" : "MTL"
>     ,"output" : [ "full_hostname", "domain_without_subdomains" ]
>     ,"config" : {
>       "full_hostname" : “URL_TO_HOST(123)"
>       ,"domain_without_subdomains" : "DOMAIN_REMOVE_SUBDOMAINS(full_hostname)"
>                 }
>     }
>                            ]
> }
> ----------------------------------------------------------------------------------------------------
> Replay Squid events/logs and monitor the logs in storm for squid topology.
> Attached exception log would be seen and no indexes would be created 
> respective to the logs.
> Expected Behaviour :-
> 1.The error should be more clean.
> 2.Since we cannot validate the inputs the invalid inputs should be ignored 
> and the indices should get created anyway based on the Grok parser output 
> Regards,
> Neha



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to