[jira] [Commented] (IGNITE-959) Indexing: avoid sending key-value class definitions to servers when starting a cache

["Sergi Vladykin (JIRA)" <ji...@apache.org>]

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

Sergi Vladykin commented on IGNITE-959:
---------------------------------------

Yes, it seems that we should generate CacheTypeMetadata.
Inside of CacheTypeMetadata we use classes, so all user classes there must be masked as Object while all SQL-compatible classes must be stored as is.
To check SQL compatibility we need to use GridQueryIndexing.isSqlType method.

> Indexing: avoid sending key-value class definitions to servers when starting a cache
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-959
>                 URL: https://issues.apache.org/jira/browse/IGNITE-959
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache
>            Reporter: Alexey Goncharuk
>             Fix For: sprint-6
>
>
> Currently when indexed types are set to cache configuration, we send them to server nodes. It defeats the purpose of optimized marshaller improvements.
> Instead, we should analyze class annotations on clients, convert them to metadata and use this metadata on servers.



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