[ https://issues.apache.org/jira/browse/IGNITE-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293003#comment-15293003 ]
ASF GitHub Bot commented on IGNITE-3154: ---------------------------------------- GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/737 IGNITE-3154 - More efficient field lookup in binary protocol. Added i… …nterface method to BinaryObject that uses cached BinaryType for creating BinaryFiled. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3154 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/737.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #737 ---- commit 019d2dc6569958d37aa6719429fba09edc203ec2 Author: dkarachentsev <dkarachent...@gridgain.com> Date: 2016-05-20T08:29:58Z IGNITE-3154 - More efficient field lookup in binary protocol. Added interface method to BinaryObject that uses cached BinaryType for creating BinaryFiled. ---- > 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)