You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (Jira)" <ji...@apache.org> on 2021/06/04 16:13:00 UTC
[jira] [Updated] (NIFI-8658) Allow for filtering functions to be
used as top-level functions for RecordPath
[ https://issues.apache.org/jira/browse/NIFI-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Payne updated NIFI-8658:
-----------------------------
Status: Patch Available (was: Open)
> 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
> Time Spent: 10m
> 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)