[IGNITE-2191] Binary marshaller: support user classes with the same simple name

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: ignite-1.4
• Fix Version/s: 1.6
• Component/s: cache
• Labels: important
• Assignee: Artem Shutak
• Reporter: Denis A. Magda
• Created: 17/Dec/15 11:22
• Updated: 11/Apr/16 13:59
• Resolved: 02/Feb/16 18:06

Description

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.

Issue Links

• blocks: IGNITE-2398 .NET: Change default mapper behavior
• is related to: IGNITE-2395 Binary marshaller: id mapper must be resolved according to configuration.

Sub-Tasks

• .NET: Change default mapper behavior: Resolved