nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-4257) Allow a custom WHERE clause in AbstractDatabaseFetchProcessor
Date Thu, 07 Sep 2017 18:48:00 GMT

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

ASF GitHub Bot commented on NIFI-4257:
--------------------------------------

Github user mattyb149 commented on the issue:

    https://github.com/apache/nifi/pull/2050
  
    +1 LGTM, ran build and unit tests (and contrib-check), also tested both GenerateTableFetch
and QueryDatabaseTable with MySQL and Oracle DBs and various WHERE clauses. Great work! Merging
to master


> 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
>             Fix For: 1.4.0
>
>
> 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)

Mime
View raw message