You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/07 15:24:00 UTC
[jira] [Commented] (NIFI-4257) Allow a custom WHERE clause in
AbstractDatabaseFetchProcessor
[ https://issues.apache.org/jira/browse/NIFI-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157084#comment-16157084 ]
ASF GitHub Bot commented on NIFI-4257:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2050
Do you mind rebasing this against the latest master? the code LGTM so will run it once it builds cleanly, and merge if all is well, thanks in advance!
> Allow a custom WHERE clause in AbstractDatabaseFetchProcessor
> -------------------------------------------------------------
>
> Key: NIFI-4257
> URL: https://issues.apache.org/jira/browse/NIFI-4257
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
>
> It could be useful allowing a user to set a custom WHERE clause in AbstractDatabaseFetchProcessor in case not all of the data in the table is required.
> In case the WHERE clause is changed after the processor has already been running, the user will probably have to set the initial maximum values to ensure the expected behaviour.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)