nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Witt (JIRA)" <>
Subject [jira] [Commented] (NIFI-3335) GenerateTableFetch should allow you to specify an initial Max Value
Date Fri, 11 Aug 2017 01:32:00 GMT


Joseph Witt commented on NIFI-3335:

Ok it appears the db for JIRA for this ticket is wacky.  Can be fixed if done by an admin.
 Rather than bothering ASF admins just cloned it and ported the history/log there.  Will still
be searchable by those comments.  Deleting this JIRA.

> GenerateTableFetch should allow you to specify an initial Max Value
> -------------------------------------------------------------------
>                 Key: NIFI-3335
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Matt Burgess
>            Assignee: Joseph Witt
> 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
> This feature would also be helpful in GenerateTableFetch, which also supports max-value
> 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

View raw message