[jira] [Commented] (NIFI-6865) Add Fetch Size property to ExecuteSQL processors

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on NIFI-6865:
-------------------------------------------------------

Commit d617c0b96ab5d2f42c467643aa55cc4ab9a70b27 in nifi's branch refs/heads/master from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d617c0b ]

NIFI-6865: Added Fetch Size property to ExecuteSQL processors

This closes #3888.

Signed-off-by: Peter Turcsanyi <tu...@apache.org>


> Add Fetch Size property to ExecuteSQL processors
> ------------------------------------------------
>
>                 Key: NIFI-6865
>                 URL: https://issues.apache.org/jira/browse/NIFI-6865
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The ExecuteSQL and ExecuteSQLRecord processors do 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 10|https://docs.oracle.com/cd/E18283_01/java.112/e16548/resltset.htm#i1023619], which means result rows needs to be fetched ten 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
(v8.3.4#803005)