[
https://issues.apache.org/jira/browse/NIFI-7803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198043#comment-17198043
]
ASF subversion and git services commented on NIFI-7803:
-------------------------------------------------------
Commit 6aa58d1374129f723dc5130ab88da10d1f755c94 in nifi's branch
refs/heads/support/nifi-1.12.x from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6aa58d1 ]
NIFI-7803: Allow ExecuteSQL(Record) properties to evaluate flowfile attributes
where possible
Signed-off-by: Pierre Villard <pierre.villard...@gmail.com>
This closes #4523.
> Allow ExecuteSQL(Record) properties to evaluate flowfile attributes where
> possible
> ----------------------------------------------------------------------------------
>
> Key: NIFI-7803
> URL: https://issues.apache.org/jira/browse/NIFI-7803
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Minor
> Fix For: 1.13.0, 1.12.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Some properties in ExecuteSQL and ExecuteSQLRecord only evaluate variables
> and not flowfile attributes, even if the values are obtained per-flowfile (in
> onTrigger, e.g.). In these cases, it would make the processors more flexible
> if those properties could evaluate flowfile attributes as well. A use case is
> for multiple tables with varying number of columns and rows, when the overall
> output flowfile size is desired to be around the same for each flow file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
