You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (Jira)" <ji...@apache.org> on 2021/05/05 13:40:00 UTC
[jira] [Commented] (IGNITE-14683) Binary type registration fails
when class present in different packages with simple name mapper
[ https://issues.apache.org/jira/browse/IGNITE-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339663#comment-17339663 ]
Ilya Kasnacheev commented on IGNITE-14683:
------------------------------------------
It may seem that Ignite need to map simple type to complete type, but if query entities/indexed types are used, complete type is known to Ignite anyway, for a specific cache. So no collision may indeed happen unless the types are stored in the same cache (which they were not).
> Binary type registration fails when class present in different packages with simple name mapper
> -----------------------------------------------------------------------------------------------
>
> Key: IGNITE-14683
> URL: https://issues.apache.org/jira/browse/IGNITE-14683
> Project: Ignite
> Issue Type: Bug
> Components: binary
> Affects Versions: 2.8
> Reporter: Ilya Kasnacheev
> Priority: Major
>
> The following exception will be caught:
> IgniteCheckedException: Failed to merge new and existing marshaller mappings. For [platformId=0, typeId=12345689] new typeName=com.pany.services.restApi.ContactList, existing typeName=com.pany.services.handler.Contactlist
> It is expected that there is no metadata conflict and simple name is always used, if possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)