You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2016/03/13 17:30:33 UTC
[jira] [Resolved] (FLINK-3472) JDBCInputFormat.nextRecord(..) has
misleading message on NPE
[ https://issues.apache.org/jira/browse/FLINK-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-3472.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.0.1
1.1.0
Fixed in
- 1.0.1 via 3d8c7c1ea0791a1f3243d8f0094cb2947c028674
- 1.1.0 via e719eddb9606351baccb45491f473563c2fe61fa
> JDBCInputFormat.nextRecord(..) has misleading message on NPE
> ------------------------------------------------------------
>
> Key: FLINK-3472
> URL: https://issues.apache.org/jira/browse/FLINK-3472
> Project: Flink
> Issue Type: Bug
> Affects Versions: 0.10.2
> Reporter: Ken Geis
> Assignee: Chesnay Schepler
> Priority: Minor
> Fix For: 1.1.0, 1.0.1
>
>
> JDBCInputFormat.nextRecord(..) assumes that a NullPointerException could only occur by the resultSet being null. It rethrows an exception with the message "Couldn't access resultSet". See FLINK-3471 for an example of where the NPE could come from another situation. Either the message should be changed or the scope of the try/catch should be tightened around the {{resultSet.next();}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)