nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Payne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-485) EvaluateJsonPath: should allow user to choose how to handle missing JsonPath
Date Sun, 05 Apr 2015 19:40:33 GMT

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

Mark Payne commented on NIFI-485:
---------------------------------

Not a problem. The whole point of this really was to allow me to say "Don't warn if the JSON
Path doesn't match - it's normal in my use case." Right now, though, it also always routes
to "matched" if using attributes. Might make sense to allow it to route to "unmatched" in
this case as well.

> EvaluateJsonPath: should allow user to choose how to handle missing JsonPath
> ----------------------------------------------------------------------------
>
>                 Key: NIFI-485
>                 URL: https://issues.apache.org/jira/browse/NIFI-485
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Mark Payne
>             Fix For: 0.1.0
>
>         Attachments: 0001-NIFI-485-EvaluateJsonPath-should-allow-user-to-choos.patch
>
>
> If EvaluateJsonPath is used and configured to write results to attributes, but the JsonPath
does not match, it logs at a WARNING level and then moves on. Instead, user should be presented
with options on how to handle this. Would recommend the user be able to choose one of:
> * Route to 'no.match'
> * Warn on Condition
> * Ignore



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

Mime
View raw message