accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2758) LocalityGroupUtil.encodeColumnFamily() ignores offset parameter
Date Fri, 16 May 2014 11:00:04 GMT

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

ASF subversion and git services commented on ACCUMULO-2758:
-----------------------------------------------------------

Commit b2ecd1cdbe0cfe4f14c6be7a38b7113897654dc7 in accumulo's branch refs/heads/1.5.2-SNAPSHOT
from [~gary2086]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=b2ecd1c ]

ACCUMULO-2758 Remove non-observed offset argument from private encodeColumnFamily method

Signed-off-by: Josh Elser <elserj@apache.org>


> LocalityGroupUtil.encodeColumnFamily() ignores offset parameter
> ---------------------------------------------------------------
>
>                 Key: ACCUMULO-2758
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2758
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.4.5, 1.5.1
>            Reporter: Bill Havanki
>            Assignee: Gary Singh
>            Priority: Minor
>              Labels: newbie
>             Fix For: 1.5.2, 1.6.1, 1.7.0
>
>         Attachments: ACCUMULO-2758-2.patch, ACCUMULO-2758.patch
>
>
> The method {{LocalityGroupUtil.encodeColumnFamily(ByteSequence)}} heeds the current offset
and length of the byte sequence, passing them to an private method that does the encoding.
However, the private method ignores its offset parameter, and always starts from the beginning
of the byte array.
> Fortunately, it appears that there are no callers for the public method, and the other
caller of the private method always passes an offset of zero. So, the bug is probably not
expressed. The method with the bug should probably just be eliminated.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message