ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (IGNITE-2213) Handle duplicate field names in BinaryMarshaller.
Date Tue, 22 Dec 2015 08:28:46 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vladimir Ozerov closed IGNITE-2213.
-----------------------------------

> Handle duplicate field names in BinaryMarshaller.
> -------------------------------------------------
>
>                 Key: IGNITE-2213
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2213
>             Project: Ignite
>          Issue Type: Bug
>          Components: general, interop
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>            Priority: Blocker
>             Fix For: 1.5
>
>
> Consider the following scenario:
> {code}
> class A {
>     int field;
> }
> class B : class A {
>     int field;
> }
> {code}
> In this case BinaryMarshaller will throw an exception about duplicate field names. And
there is no sensible workaround for user. 
> We can add some prefix/suffix to comflicting fields. E.g. A.field will be written as
"field", B.field will be written as "field_B".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message