[
https://issues.apache.org/jira/browse/CALCITE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404316#comment-16404316
]
ASF GitHub Bot commented on CALCITE-2219:
-----------------------------------------
Github user laurentgo commented on a diff in the pull request:
https://github.com/apache/calcite-avatica/pull/33#discussion_r175320462
--- Diff:
core/src/main/java/org/apache/calcite/avatica/AvaticaConnection.java ---
@@ -276,14 +298,17 @@ public CallableStatement prepareCall(
}
public Map<String, Class<?>> getTypeMap() throws SQLException {
- throw HELPER.unsupported();
+ checkOpen();
+ // Always return an empty map since custom types is not supported
+ return new HashMap<>();
--- End diff --
yes, probably more correct. I think I got the truncated version of the
javadoc on this one. I will revert.
> Avatica Connection/Statement/ResultSet don't throw if resource is closed
> ------------------------------------------------------------------------
>
> Key: CALCITE-2219
> URL: https://issues.apache.org/jira/browse/CALCITE-2219
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Laurent Goujon
> Assignee: Laurent Goujon
> Priority: Major
>
> According to JDBC spec/Javadoc, almost all methods of
> {{Connection}}/{{Statement}}/{{PreparedStatement}}/{{ResultSet}} should throw
> an exception if resource is closed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
