You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/07 02:39:10 UTC
[jira] [Commented] (NIFI-2157) Add GenerateTableFetch processor
[ https://issues.apache.org/jira/browse/NIFI-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365501#comment-15365501 ]
ASF GitHub Bot commented on NIFI-2157:
--------------------------------------
GitHub user mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/613
NIFI-2157: Add GenerateTableFetch processor
NOTE: This PR depends on #599. I put the DB-specific stuff in an interface and used ServiceLoader to get at them, but I welcome your comments perhaps on adding it to the DBCPService interface for example. I didn't want to overkill here, but if we end up with more processors that need a DB-specific interface, I wanted to make sure it was more generic. Perhaps it belongs in nifi-api or something in that case.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattyb149/nifi NIFI-2157
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/613.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #613
----
commit c33da1d7f3635225f74ae4a722fbb49440e5e72a
Author: Matt Burgess <ma...@apache.org>
Date: 2016-07-07T02:34:37Z
NIFI-2156: Add ListDatabaseTables processor
commit 4037dbe540df0d3f98927cd66296f1310c53b9ef
Author: Matt Burgess <ma...@apache.org>
Date: 2016-07-07T02:35:55Z
NIFI-2157: Add GenerateTableFetch processor
----
> Add GenerateTableFetch processor
> --------------------------------
>
> Key: NIFI-2157
> URL: https://issues.apache.org/jira/browse/NIFI-2157
> Project: Apache NiFi
> Issue Type: Sub-task
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Fix For: 1.0.0
>
>
> This processor would presumably have a ListDatabaseTables in front of it and will use the same DatabaseConnectionPool service. It will read the aforementioned attributes along with an optional "Partition Size" property (which accepts Expression Language). The information is used to generate flow files containing SQL statements that will select rows from a table. If the partition size is indicated, then the SELECT statements will refer to a range of rows, such that each statement will grab only a portion of the table. These flow files (due to NIFI-1973) can be passed to ExecuteSQL processors for the actual fetching of rows.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)