You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2016/03/01 11:46:18 UTC

[jira] [Commented] (IGNITE-1419) .Net: Add optional "raw" flag to binary type configuration.

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

Pavel Tupitsyn commented on IGNITE-1419:
----------------------------------------

1) This property should be readonly, that's why ctor arg is necessary. If the property is writeable, and user sets it after type registration, it won't take effect.
The "too many ctor args" problem has other solutions (introduce a struct to hold args).
2) Done

> .Net: Add optional "raw" flag to binary type configuration.
> -----------------------------------------------------------
>
>                 Key: IGNITE-1419
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1419
>             Project: Ignite
>          Issue Type: Task
>          Components: platforms
>    Affects Versions: 1.1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Pavel Tupitsyn
>             Fix For: 1.6
>
>
> By default we write .Net objects with field names included. But in some cases it is not needed. E.g. when objects are not going to be used in queries.
> Removing field names will speed up serialization/deserialization. We can add optional "raw" flag to portable type descriptor to control this behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)