[ 
https://issues.apache.org/jira/browse/NIFI-8273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419195#comment-17419195
 ] 

ASF subversion and git services commented on NIFI-8273:
-------------------------------------------------------

Commit 5b7af511fc1187676d5e0eefe7c3899ef102246d in nifi's branch 
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5b7af51 ]

NIFI-8273: Fix typos in docs/clarify some statements. Addressed handling of 
arrays as partitions

This closes #4948.


> Adding Scripted Record processors
> ---------------------------------
>
>                 Key: NIFI-8273
>                 URL: https://issues.apache.org/jira/browse/NIFI-8273
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Simon Bence
>            Assignee: Simon Bence
>            Priority: Major
>          Time Spent: 10h 40m
>  Remaining Estimate: 0h
>
> The *ScriptedTransformRecord* was recently added which we can use as a 
> starting point for a few additional scripted processors for common tasks. 
> These might be:
>  * *ScriptedPartitionRecord*. Given a Record, would return the name of a 
> 'partition' to send to. Two Records from an incoming FlowFile will go to the 
> same outbound FlowFile if they belong to the same Partition.
>  * *ScriptedValidateRecord*. Given a record, return true or false to indicate 
> whether it should go to 'valid' or 'invalid'. This is less powerful and can 
> easily be encapsulated within the previous one. However, it might make sense 
> to provide it anyway, just because if you want to validate a record, it's 
> more obvious that this is the right processor.
>  * *ScriptedFilterRecord*. Given a Record, returns {{true}} to keep the 
> Record, {{false}} to drop the Record. Can already be done using the 
> ScriptedTransformRecord by returning {{null}}. But it does make sense to 
> offer this anyway from a user experience point of view
> All the above processors are very similar in functionalities and encapsulate 
> each other. However the idea is to provide a set of processors that are 
> obvious to use even if there is one that could answer all the needs by 
> tweaking the configuration.



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

Reply via email to