[jira] [Updated] (NIFI-485) EvaluateJsonPath: should allow user to choose how to handle missing JsonPath

["Jon Anderson III (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon Anderson III updated NIFI-485:
----------------------------------
    Attachment: 0001-NIFI-485-EvaluateJsonPath-should-allow-user-to-choos.patch

Attached is a patch I "think" will work. I'll be honest. I don't know much Java (well at all). So any constructive feedback would be appreciated. 

There's a new property that has four settings:

warn - log an error and pass the flowfile to unmatched
route to failure - route flow file to failure when path isn't found
route to matched - route flow file to matched when path isn't found
route to unmatched - route flow file to unmatched when path isn't found

I'm sort of torn on if that's too many possible values. I suppose worst case it's super flexible :) 



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