[
https://issues.apache.org/jira/browse/IGNITE-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098635#comment-15098635
]
Artem Shutak commented on IGNITE-2191:
--------------------------------------
Finished with implementation.
Also found and fixed the following bug: {{BinaryContext.typeId(typeName)}}
method uses the default IdMapper for not registered types in process of
initialization instead of calculating idMapper according to configuration.
Waiting for TC results. WIll fix tests and will write new ones.
> Binary marshaller: support user classes with the same simple name
> -----------------------------------------------------------------
>
> Key: IGNITE-2191
> URL: https://issues.apache.org/jira/browse/IGNITE-2191
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: ignite-1.4
> Reporter: Denis Magda
> Assignee: Artem Shutak
> Priority: Critical
> Labels: important
> Fix For: 1.6
>
>
> Presently the user won't be able to use across the cluster object that have a
> single simple name.
> As an example if the user has 'org.comp.MyObject' and
> 'org.apache.comp.MyObject' then he won't be able to have them both in a
> cluster because marshalling mechanism supports uniqueness at simple name
> level only.
> There are several reasons for that:
> - interoperability with other platforms;
> - queries that use simple name is their 'where' clause.
> In general according to the API as a workaround the user can implement its
> own BinaryIdMapper returning a precise id for every class. However there is a
> bug in BinaryContext that passes simple name rather than a full name to a
> BinaryIdMapper implementation. BinaryIdMapper must be fixed as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
