[ 
https://issues.apache.org/jira/browse/NIFI-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201271#comment-16201271
 ] 

Koji Kawamura commented on NIFI-4457:
-------------------------------------

[~mehrdad22] Would you be able to share followings with us to nail it down the 
cause of this issue:

# To understand and confirm the situation, before starting QueryDatabaseTable,
## Capture QueryDatabaseTable config and state (as you did before with the 
attached screenshot)
## Execute a SQL query directly to the source table using the 
'initial.maximum.xxxx' value specified at QueryDatabaseTable, for example: 
{code}SELECT * FROM tweets_json WHERE tweet_id > 111111111111111111{code} This 
query ensures there're new records those should be fetched by 
QueryDatabaseTable. Please share query and its result. (The example query 
should return rows having grater tweet_id such as 111111111111111112)
# After starting QueryDatabaseTable, please confirm following conditions:
## QueryDatabaseTable state has NOT been updated as reported

Having a reproducible dataset and operations is really helpful for us to fix 
the issue.

> "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)

Reply via email to