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 2022/01/21 10:06:00 UTC

[jira] [Updated] (IGNITE-16341) .NET: Thin 3.0: Emit efficient POCO serialization code

     [ https://issues.apache.org/jira/browse/IGNITE-16341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Tupitsyn updated IGNITE-16341:
------------------------------------
    Description: 
Initial POCO serialization (IGNITE-16227) uses a simple but inefficient reflection API. 
* Use *Reflection.Emit* to compile efficient POCO serialization code for user types.
* Use fields instead of properties to support read-only classes, records, and so on.
* Update XMLDoc for *ITable.GetRecordView* and explain how the mapping works.
* Consider a way to provide custom column names for mapped classes - attributes or converters (separate ticket?)

  was:
Initial POCO serialization (IGNITE-16227) uses a simple but inefficient reflection API. 
Use *Reflection.Emit* to compile efficient POCO serialization code for user types.


> .NET: Thin 3.0: Emit efficient POCO serialization code
> ------------------------------------------------------
>
>                 Key: IGNITE-16341
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16341
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms, thin client
>    Affects Versions: 3.0.0-alpha5
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: .NET, ignite-3
>             Fix For: 3.0.0-alpha5
>
>
> Initial POCO serialization (IGNITE-16227) uses a simple but inefficient reflection API. 
> * Use *Reflection.Emit* to compile efficient POCO serialization code for user types.
> * Use fields instead of properties to support read-only classes, records, and so on.
> * Update XMLDoc for *ITable.GetRecordView* and explain how the mapping works.
> * Consider a way to provide custom column names for mapped classes - attributes or converters (separate ticket?)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)