[jira] [Commented] (NIFI-1706) Extend QueryDatabaseTable to support arbitrary queries

["Koji Kawamura (JIRA)" <ji...@apache.org>]

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

Koji Kawamura commented on NIFI-1706:
-------------------------------------

Hi [~peebor@gmail.com] [~patricker],

I found a similar JIRA NIFI-2200 before I found this one. I closed NIFI-2200 as I believe VIEWs can replace sub-query needs. VIEWs can cover the improvements requested by this JIRA, too. I personally prefer to keep a processor implementation as simple as possible for sustainable maintainability. I appreciate Peter's work but wanted to discuss. How do you think? Thank you.

> Extend QueryDatabaseTable to support arbitrary queries
> ------------------------------------------------------
>
>                 Key: NIFI-1706
>                 URL: https://issues.apache.org/jira/browse/NIFI-1706
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.4.0
>            Reporter: Paul Bormans
>            Assignee: Peter Wicks
>            Priority: Major
>              Labels: features
>
> The QueryDatabaseTable is able to observe a configured database table for new rows and yield these into the flowfile. The model of an rdbms however is often (if not always) normalized so you would need to join various tables in order to "flatten" the data into useful events for a processing pipeline as can be build with nifi or various tools within the hadoop ecosystem.
> The request is to extend the processor to specify an arbitrary sql query instead of specifying the table name + columns.
> In addition (this may be another issue?) it is desired to limit the number of rows returned per run. Not just because of bandwidth issue's from the nifi pipeline onwards but mainly because huge databases may not be able to return so many records within a reasonable time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)