You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2017/08/11 00:29:00 UTC
[jira] [Commented] (NIFI-3335) GenerateTableFetch should allow you
to specify an initial Max Value
[ https://issues.apache.org/jira/browse/NIFI-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16122606#comment-16122606 ]
Joseph Witt commented on NIFI-3335:
-----------------------------------
i dont see an obvious way to close it either. will try some things...weird
> 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
> Fix For: 1.4.0
>
>
> 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)