[
https://issues.apache.org/jira/browse/IGNITE-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727351#comment-14727351
]
ASF GitHub Bot commented on IGNITE-1353:
----------------------------------------
GitHub user dmagda opened a pull request:
https://github.com/apache/ignite/pull/59
ignite-1353: fixed type resolving conflicts in portable context
Refer to https://issues.apache.org/jira/browse/IGNITE-1353 for more details.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dmagda/incubator-ignite ignite-1353
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/59.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #59
----
commit c1d60ad1644482992490146f768479d601b2d197
Author: Denis Magda <dma...@gridgain.com>
Date: 2015-09-02T13:32:08Z
ignite-1353: fixed type resolving conflicts between predefined and user
types
----
> PortableContext.typeId() incorrectly resolves type ID for predefined system
> types.
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-1353
> URL: https://issues.apache.org/jira/browse/IGNITE-1353
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 1.1.4
> Reporter: Vladimir Ozerov
> Assignee: Denis Magda
> Priority: Critical
> Fix For: ignite-1.4
>
>
> See PortableContext.typeId() method.
> First it checks whether type is "system", and only then try picking
> predefiend ID. As a result, predefined types like IgniteBiTuple are written
> with wrong IDs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
