[
https://issues.apache.org/jira/browse/NIFI-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357649#comment-17357649
]
ASF subversion and git services commented on NIFI-8658:
-------------------------------------------------------
Commit c9dee3029422a172c181d6c2d8d8e54e2ecd013e in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c9dee30 ]
NIFI-8658: Allow Filter Functions and expressions to be specified as a
RecordPaths
NIFI-8658: Addressed issue where the RecordField that was provided from
Function Filters were not accurate
Signed-off-by: Matthew Burgess <[email protected]>
This closes #5125
> Allow for filtering functions to be used as top-level functions for RecordPath
> ------------------------------------------------------------------------------
>
> Key: NIFI-8658
> URL: https://issues.apache.org/jira/browse/NIFI-8658
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.14.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> RecordPath allows for filtering functions such as {{isEmpty}} to be used only
> within a predicate. So something like {{isEmpty(/name}}) is not a valid
> RecordPath, while {{/[isEmpty(./name)]}} is a valid RecordPath. This makes
> sense for most use cases. However, for cases where we may want to partition
> based on a RecordPath, having the ability to partition based on
> {{isEmpty(/name)}} can be important.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
