[
https://issues.apache.org/jira/browse/PHOENIX-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542306#comment-14542306
]
Josh Mahonin commented on PHOENIX-1968:
---------------------------------------
Hmm, I just noticed that I've slightly altered the previous statement:
{code}
statement.setObject(i + 1, finalObj, finalType)
{code}
to
{code}
statement.setObject(i + 1, finalObj)
{code}
The unit tests still pass though, does anyone know if there are any cases where
setting the sql type is explicitly required?
> Phoenix-Spark: Should support saving arrays
> -------------------------------------------
>
> Key: PHOENIX-1968
> URL: https://issues.apache.org/jira/browse/PHOENIX-1968
> Project: Phoenix
> Issue Type: Bug
> Reporter: Josh Mahonin
> Assignee: Josh Mahonin
> Attachments: PHOENIX-1968.patch
>
>
> At present, we only use 'setObject' on the PreparedStatement when writing
> back to Phoenix. This patch allows calling 'setArray' with the appropriate
> sql base type when an array is passed in as a column value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
