[
https://issues.apache.org/jira/browse/IGNITE-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935268#comment-14935268
]
Alexey Goncharuk commented on IGNITE-950:
-----------------------------------------
My original design with adding methods on the Marshaller interface does not
really work well because in order to truly plug into cache mechanics the cache
object manager (introduced) should be pluggable.
Since we still want to configure a marshaller per cache, I suggest using an
annotation attached to a marshaller indicating that another cache object
manager should be used for a cache:
{code}
@CacheObjectManager(PortableObjectManager.class)
public class PortableMarshaller extends MarshallerAdapter {
}
{code}
> OptimizedMarshaller: add ability to unmarshal a particular field
> ----------------------------------------------------------------
>
> Key: IGNITE-950
> URL: https://issues.apache.org/jira/browse/IGNITE-950
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Affects Versions: sprint-5
> Reporter: Denis Magda
> Assignee: Alexey Goncharuk
> Fix For: ignite-1.5
>
>
> When field names of an object are used in SQL, text or other kind of queries,
> object, that owns a field, is fully deserialized.
> This is bad from performance perspective.
> The task is to support peer field deserialization by looking it up in a
> marshalled byte array and unmarshalling it from a concrete offset with
> OptimizedMarshaller later.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
