You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2015/09/02 15:36:45 UTC

[jira] [Commented] (IGNITE-1353) PortableContext.typeId() incorrectly resolves type ID for predefined system types.

    [ https://issues.apache.org/jira/browse/IGNITE-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727345#comment-14727345 ] 

Denis Magda commented on IGNITE-1353:
-------------------------------------

Fixed conflicts between system, predefined and user types resolution.

Also found one more issue that required changes in the protocol - IGNITE-1358.
Implemented workaround as a part of this task until IGNITE-1358 is fixed.

Checking the changes with TC. 

> 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)