[
https://issues.apache.org/jira/browse/NIFI-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214396#comment-15214396
]
ASF GitHub Bot commented on NIFI-1691:
--------------------------------------
GitHub user mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/307
NIFI-1691: Add Fetch Size property to QueryDatabaseTable
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattyb149/nifi querydb-fetchsize
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/307.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 #307
----
commit 5ea45e89b657d854cd287c58d94c83342ecc278f
Author: Matt Burgess <[email protected]>
Date: 2016-03-28T16:16:24Z
NIFI-1691: Add Fetch Size property to QueryDatabaseTable
----
> Add Fetch Size property to QueryDatabaseTable processor
> -------------------------------------------------------
>
> Key: NIFI-1691
> URL: https://issues.apache.org/jira/browse/NIFI-1691
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 0.6.0
> Reporter: Matt Burgess
> Assignee: Matt Burgess
>
> The QueryDatabaseTable processor does not have a way for the user to set the
> fetch size for the JDBC query. Some drivers (like Oracle) default to a fetch
> size of 1, which means result rows needs to be fetched one at a time from the
> database. This can be very slow, an improvement would be to allow the user to
> set the fetch size for the query.
> NOTE: Some drivers do not support this, either by throwing an exception or
> ignoring it (the JDBC spec marks it as a "hint to the database", the doc for
> the property should make this clear and no exception should be propagated
> through the processor if the attempt to set fetch size is unsuccessful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
