[
https://issues.apache.org/jira/browse/GEODE-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406055#comment-17406055
]
ASF subversion and git services commented on GEODE-9555:
--------------------------------------------------------
Commit 39e74135ca62817293e61b6c4cbdc538e0fb4ffb in geode's branch
refs/heads/develop from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=39e7413 ]
GEODE-9555: optimize incr/decr results (#6778)
RedisString and RedisHash incr/decr ops now return byte[] instead of long
saving an extra conversion.
> the redis commands that increment or decrement using a long do an extra
> conversion
> ----------------------------------------------------------------------------------
>
> Key: GEODE-9555
> URL: https://issues.apache.org/jira/browse/GEODE-9555
> Project: Geode
> Issue Type: Improvement
> Components: redis
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> The redis commands that increment or decrement using a long end up storing
> the new value in the RedisData instance as an ascii byte array. They are also
> required to return that value to the client. When geode's implementation
> returns the value, it currently does so as a "long" instead of as a "byte[]".
> This forces the code later on to call Coder.longToBytes again. Since we
> already have it in the correct form we should return that to the caller so
> that it can just copy the bytes instead of needing to compute them again.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
