[ https://issues.apache.org/jira/browse/NIFI-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102795#comment-16102795 ]
ASF subversion and git services commented on NIFI-3335: ------------------------------------------------------- Commit dc4006f423b83e7819981569d17e8d90b9a9d1a4 in nifi's branch refs/heads/master from [~mattyb149] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=dc4006f ] NIFI-3335: Add initial.maxvalue support to GenerateTableFetch Signed-off-by: Pierre Villard <pierre.villard...@gmail.com> This closes #2039. > GenerateTableFetch should allow you to specify an initial Max Value > ------------------------------------------------------------------- > > Key: NIFI-3335 > URL: https://issues.apache.org/jira/browse/NIFI-3335 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions > Reporter: Matt Burgess > Assignee: Matt Burgess > > NIFI-2583 added the ability (via dynamic properties) to specify initial Max > Values for columns, to enable the user to "pick up where they left off" if > something happened with a flow, a NiFi instance, etc. where the state was > stored but the processing did not complete successfully. > This feature would also be helpful in GenerateTableFetch, which also supports > max-value columns. > Since NIFI-2881 adds incoming flow file support, it's more useful if Initial > max values can be specified via flow file attributes. Because if a table name > is dynamically passed via flow file attribute and Expression Language, user > won't be able to configure dynamic processor attribute in advance for each > possible table. > Add dynamic properties ('initial.maxvalue.<max_value_column>' same as > QueryDatabaseTable) to specify initial max values statically, and also use > incoming flow file attributes named 'initial.maxvalue.<max_value_column>' if > any. -- This message was sent by Atlassian JIRA (v6.4.14#64029)