[
https://issues.apache.org/jira/browse/NIFI-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411918#comment-17411918
]
ASF subversion and git services commented on NIFI-8376:
-------------------------------------------------------
Commit 98e3b465c3f94bf693b57808b05cc715fba18855 in nifi's branch
refs/heads/main from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=98e3b46 ]
NIFI-8376: Gracefully handle SQL exceptions in ResultSetRecordSet
This closes #4951
Signed-off-by: Mike Thomsen <[email protected]>
> Gracefully handle SQL exceptions in ResultSetRecordSet
> ------------------------------------------------------
>
> Key: NIFI-8376
> URL: https://issues.apache.org/jira/browse/NIFI-8376
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> There is code in ResultSetRecordSet to call the JDBC API method isAfterLast()
> when attempting to determine the element type for an array. It is called to
> avoid possible exceptions later when getArray() is called.
> However because isAfterLast() is a JDBC API method, it too may be unsupported
> by drivers (and at the time of this writing, it is unsupported by the Presto
> JDBC driver). This defeats the purpose of the defensive code and can cause
> its own issues.
> This code should be refactored to more gracefully handle "not supported"
> exceptions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
