[
https://issues.apache.org/jira/browse/CALCITE-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518565#comment-16518565
]
Miles Spielberg commented on CALCITE-2362:
------------------------------------------
I'm afraid I don't. We experienced this in the context of Phoenix, and don't
have a standalone Avatica setup. I can look at creating a unit test, but I've
not looked at the codebase yet beyond tracing the failure by hand on Github.
> PreparedStatement.setObject does not handle Array
> -------------------------------------------------
>
> Key: CALCITE-2362
> URL: https://issues.apache.org/jira/browse/CALCITE-2362
> Project: Calcite
> Issue Type: Bug
> Reporter: Miles Spielberg
> Assignee: Julian Hyde
> Priority: Major
>
> Currently setObject() infers the type of the parameter by calling
> TypedValue.ofJdbc, which delegates to Rep.of(value.getClass()) to do a lookup
> in VALUE_MAP. VALUE_MAP contains an entry for java.sql.Array, but this is an
> interface type, which can never match the actual class of
> avatica.util.ArrayImpl.
> Instead the implementation falls back to OBJECT, which then fails during
> serialization.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
