You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2015/04/19 15:34:58 UTC

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

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

Aldrin Piri resolved NIFI-485.
------------------------------
    Resolution: Fixed

> 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-Allow-for-the-disabling-of-warnings-when-path-is-not.patch, 0001-NIFI-485-EvaluateJsonPath-should-allow-user-to-choos.patch, 0001-Path-not-found-behavior-and-style-corrections.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)