[GitHub] nifi issue #1407: NIFI-2881: Added EL support to DB Fetch processors, allow ...

[mattyb149 <gi...@git.apache.org>]

Github user mattyb149 commented on the issue:

    https://github.com/apache/nifi/pull/1407
  
    If we going to add the ability to keep track of dynamic max-value properties in GenerateTableFetch, then there's really no reason why we can't do the same for QueryDatabaseTable. I left it out of the original Jira based on the premise that we wouldn't support max-value columns with incoming connections, and at that point QueryDatabaseTable would work basically like ExecuteSQL.
    The major difference in this case will be that if there is an incoming connection, then the fetch processors are purely event-driven, meaning they will need to be hydrated from upstream to get new results. If there is no incoming connection, then they will maintain their current behavior of running on their current schedule to check for new max values.  Does this sound ok?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---