[
https://issues.apache.org/jira/browse/NIFI-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424951#comment-15424951
]
ASF subversion and git services commented on NIFI-2583:
-------------------------------------------------------
Commit 1470a52b1bf3a1c2f9101306c70db0b08692301f in nifi's branch
refs/heads/master from [~patricker]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=1470a52 ]
NIFI-2582 NIFI-2583
Signed-off-by: Matt Burgess <[email protected]>
NIFI-2583 Tweaks
Signed-off-by: Matt Burgess <[email protected]>
This closes #877
> QueryDatabaseTable should allow you to specify an initial Max Value
> -------------------------------------------------------------------
>
> Key: NIFI-2583
> URL: https://issues.apache.org/jira/browse/NIFI-2583
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Peter Wicks
> Fix For: 1.0.0
>
>
> QueryDatabaseTable should allow you to specify an initial Max Value for max
> value columns. This value would be read from custom properties, added by
> users, one for each max value column that they want to provide a max value
> for.
> If a value for a column already exists in the State then this initial value
> is ignored. Clearing the state will cause the initial value to be read again.
> This will provide a method by which an operations person could stop a job,
> clear state, move the initial value for a column to an appropriate value,
> then start the job again. Thus re-ingesting all data from a certain value
> forward again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
