[
https://issues.apache.org/jira/browse/CALCITE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483711#comment-14483711
]
Julian Hyde commented on CALCITE-671:
-------------------------------------
I don't think the Jackson type information can kick in if it's a list of
Object, only if it's a list of C where C is a class that has a JsonTypeInfo
annotation.
I've been thinking that we shouldn't be sending just parameter values, but
(type, value) pairs. The type will solve the problem of, say sending a long 0
and getting an int 0 at the other end (we'd instead send {type: "long", value:
0}) and it will also give us an opportunity to create a sub-type for byte
arrays.
> ByteString does not deserialize properly as a FetchRequest parameterValue
> -------------------------------------------------------------------------
>
> Key: CALCITE-671
> URL: https://issues.apache.org/jira/browse/CALCITE-671
> Project: Calcite
> Issue Type: Bug
> Reporter: Nick Dimiduk
> Assignee: Julian Hyde
> Attachments: 671.patch
>
>
> I think the reason here is that FetchRequest#parameterValues is declared as a
> List<Object>, which Jackson interprets as a request to serialize as plain
> objects (see [Deserializing, other|http://wiki.fasterxml.com/JacksonFAQ]).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
