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 2020/11/25 19:25:00 UTC
[jira] [Assigned] (NIFI-8046) ResultSetRecordSet throws exception
on DB2
[ https://issues.apache.org/jira/browse/NIFI-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess reassigned NIFI-8046:
----------------------------------
Assignee: Matt Burgess
> ResultSetRecordSet throws exception on DB2
> ------------------------------------------
>
> Key: NIFI-8046
> URL: https://issues.apache.org/jira/browse/NIFI-8046
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
>
> Consumers of ResultSetRecordSet (such as QueryDatabaseTableRecord) can end up with an exception being thrown when processing the results. This is due to DB2 behavior that closes a ResultSet when the last row has been read, meaning next() can return true then isClosed() can return true.
> This was handled in general for the QueryDatabaseTable processors via NIFI-5303 (even though only QDT itself existed at the time, not QueryDatabaseTableRecord). However QueryDatabaseTableRecord uses ResultSetRecordSet, which calls ResultSet.next() before creating a schema from the ResultSet. On DB2 (if the result set is empty, e.g.) this results in an exception being thrown when ResultSet.getMetaData() is called from createSchema().
--
This message was sent by Atlassian Jira
(v8.3.4#803005)