[
https://issues.apache.org/jira/browse/NIFI-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190618#comment-16190618
]
Peter Wicks commented on NIFI-4457:
-----------------------------------
Thanks for reporting an issue. What your screenshot appears to show is that the
maxvalue for tweet_id you provided is already the maximum value in the table
and that there are not new records with a greater tweet_id.
After replicating the bug can you query the base table and confirm that there
are new records?
I have not been able to reproduce this. I was working with QueryDatabaseTable
yesterday, latest NiFi version, and set initial.maxvalue for about 30 tables.
None of them are being tracked by a column named `id`, and they all are working
as expected.
> "Maximum-value" not increasing when "initial.maxvalue" is set and
> "Maximum-value column" name is different from "id"
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-4457
> URL: https://issues.apache.org/jira/browse/NIFI-4457
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.3.0
> Environment: windows 10
> Reporter: meh
> Attachments: Picture1.png, Picture2.png
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> when "Maximum-value column" name is "id" there is no problem, when i add
> "initial.maxvalue.id" property in "QueryDatabaseTable" processor, it works
> well and maxvalue is increasing by every running.
> !Picture1.png|thumbnail!
> but...
> when the "Maximum-value column" name is different from "id" (such as
> "tweet_id"), after initial processor working, only given
> "initial.maxvalue.id" is saves and that repeating just same value for every
> run.
> !Picture2.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
