[ https://issues.apache.org/jira/browse/IGNITE-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291044#comment-15291044 ]
Dmitry Karachentsev commented on IGNITE-3154: --------------------------------------------- Vladimir, I don't see the correct way for using lazy metadata loading, because it may be changed in runtime and some code depends on this behavior (e.g. org.gridgain.internal.processors.dr.DrMetadataTest#testBinaryMetadataPropagation()) > More efficient field lookup in binary protocol. > ----------------------------------------------- > > Key: IGNITE-3154 > URL: https://issues.apache.org/jira/browse/IGNITE-3154 > Project: Ignite > Issue Type: Task > Components: general > Affects Versions: 1.5.0.final > Reporter: Vladimir Ozerov > Assignee: Dmitry Karachentsev > Priority: Critical > Labels: customer > Fix For: 1.7 > > > *Problem* > Currently creation of binary field is performed as follows: > {{BinaryObject.type().field(...)}}. Call to {{BinaryObject.type()}} is pretty > expensive as it requires metadata lookup. Interesting thing is that > subsequent call to {{BinaryType.field()}} doesn't require metadata at all. > *Solution* > Implement lazy metadata load for this case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)