[jira] [Updated] (NIFI-8960) Create ability for EvaluateJsonPath processor to match any or all defined json paths.

2024-03-27 Thread Michael W Moser (Jira)


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

Michael W Moser updated NIFI-8960:
--
Fix Version/s: (was: 1.14.0)
   Resolution: Won't Do
   Status: Resolved  (was: Patch Available)

Expression Language jsonPath() was built for this use case.

> Create ability for EvaluateJsonPath processor to match any or all defined 
> json paths. 
> --
>
> Key: NIFI-8960
> URL: https://issues.apache.org/jira/browse/NIFI-8960
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Tim Smith
>Assignee: Tim Smith
>Priority: Minor
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Add the capability to set "Match Criteria" to "all" or "any", where all json 
> paths must match on json objects. Default behavior being "any". Also add the 
> ability to apply to either  attributes matching regex or content, with 
> default being "match on content". 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (NIFI-8960) Create ability for EvaluateJsonPath processor to match any or all defined json paths.

2021-08-20 Thread Tim Smith (Jira)


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

Tim Smith updated NIFI-8960:

Status: Patch Available  (was: Open)

Submitted pull request:https://github.com/apache/nifi/pull/5321

> Create ability for EvaluateJsonPath processor to match any or all defined 
> json paths. 
> --
>
> Key: NIFI-8960
> URL: https://issues.apache.org/jira/browse/NIFI-8960
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Tim Smith
>Assignee: Tim Smith
>Priority: Minor
> Fix For: 1.14.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add the capability to set "Match Criteria" to "all" or "any", where all json 
> paths must match on json objects. Default behavior being "any". Also add the 
> ability to apply to either  attributes matching regex or content, with 
> default being "match on content". 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)