[
https://issues.apache.org/jira/browse/NIFI-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458997#comment-16458997
]
Nicholas Carenza commented on NIFI-5126:
----------------------------------------
Yea so if there had been a way for me to pre-populate the state that would have
also worked.
> QueryDatabaseTable state key leads to unexpected behavior when table name
> changes
> ---------------------------------------------------------------------------------
>
> Key: NIFI-5126
> URL: https://issues.apache.org/jira/browse/NIFI-5126
> Project: Apache NiFi
> Issue Type: Bug
> Environment: Nifi 1.3.0
> Reporter: Nicholas Carenza
> Priority: Major
> Attachments: image-2018-04-26-10-36-45-879.png
>
>
> I renamed a table in my database and updated my QueryDatabaseTable to match
> thinking it would resume from where it left off but the state variable name
> changed with along with the table name property.
> !image-2018-04-26-10-36-45-879.png!
> So it ended up querying the full table all over again. Can we add some
> configuration to control this behavior or remove the table name from the
> state variable by default? Since the processor can only query from one table
> anyways, I am not sure why the table name needs to be saved to state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
