[
https://issues.apache.org/jira/browse/NIFI-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192890#comment-16192890
]
meh commented on NIFI-4457:
---------------------------
[~ijokarumawak] hi.
i'm working on a database that data's are collecting by twitter API, the
application that do this work fetch whole represented json to string and save
it on other table, and request time and tweet id of that json parse into this
table i talk about it.
the logic behind twitter id's is incrementally and basically this is a proper
field for max value tracking, but if you say so, you advise me to change field
to date?
Apart from these cases, this a problem that maybe a bug and must be solved :P
> "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, subquery.csv
>
> 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)
