[
https://issues.apache.org/jira/browse/IGNITE-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067878#comment-15067878
]
Roman Shtykh commented on IGNITE-2213:
--------------------------------------
BinaryMarshallerSelfTest.testDuplicateFields() will fail in Java 8
assertEquals(1, objBin.field(fieldNameA)); -> assertEquals(new Integer(1),
objBin.field(fieldNameA)); etc.
> 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)
