You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Sivaprasanna Sethuraman (JIRA)" <ji...@apache.org> on 2018/04/27 16:10:00 UTC
[jira] [Commented] (NIFI-5126) QueryDatabaseTable state key leads
to unexpected behavior when table name changes
[ https://issues.apache.org/jira/browse/NIFI-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456681#comment-16456681 ]
Sivaprasanna Sethuraman commented on NIFI-5126:
-----------------------------------------------
This is actually expected. The reason is, as you see, the state is nothing but a Map - a key, value. The name of the table name has been used to form the key for the state map. Maybe we can have an improvement in NiFi's State management implementation to migrate or copy state and it is not a simple thing to do so need to have some discussion.
> 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)