You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (Jira)" <ji...@apache.org> on 2021/03/29 22:30:00 UTC

[jira] [Updated] (NIFI-8376) Gracefully handle SQL exceptions in ResultSetRecordSet

     [ https://issues.apache.org/jira/browse/NIFI-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess updated NIFI-8376:
-------------------------------
    Status: Patch Available  (was: In Progress)

> 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: 10m
>  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)