[
https://issues.apache.org/jira/browse/NIFI-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979211#comment-16979211
]
Shawn Weeks commented on NIFI-6865:
-----------------------------------
If anyone needs this for oracle before this patch is in a released version of
nifi you can set defaultRowPrefetch on the dbcp connection pool. I’ve tested
that on 1.9.2
> 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
> Fix For: 1.11.0
>
> Time Spent: 40m
> 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)
