ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1619) Platform .Net: Generic type is lost during array/collection serialization
Date Fri, 09 Oct 2015 10:13:26 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950165#comment-14950165

Pavel  Tupitsyn commented on IGNITE-1619:

There is another problem with this ticket: adding TypeId that is not supported in Java can
break Compute API and other things if user decides to use one of these onsupported types as
a Job argument, for example. Java part won't be able to pass it around.

Let's stop this ticket until we have an ability to pass around unsopported types in Java.

> Platform .Net: Generic type is lost during array/collection serialization
> -------------------------------------------------------------------------
>                 Key: IGNITE-1619
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1619
>             Project: Ignite
>          Issue Type: Bug
>          Components: interop
>    Affects Versions: ignite-1.4
>            Reporter: Pavel  Tupitsyn
>            Assignee: Pavel  Tupitsyn
>             Fix For: 1.5
> We do not serialize collection/array element type, so on deserialization we can not recreate
original collection. So generic arrays/collections can't be used in job arguments, service
arguments, etc.
> * We should keep current format for non-generic collections, arrays of primitives, and
arrays of objects
> * Generic collections and arrays should be written with new TypeIds (not compatible with
other platforms) and include type information

This message was sent by Atlassian JIRA

View raw message