[
https://issues.apache.org/jira/browse/CASSANDRA-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006165#comment-13006165
]
Sylvain Lebresne commented on CASSANDRA-2009:
---------------------------------------------
This is actually due to CASSANDRA-2262. The best fix to this is probably
CASSANDRA-2311, since it will also someone to say that the keys are asciiType
for instance.
> Move relevant methods to ByteBufferUtil (and normalize on names)
> ----------------------------------------------------------------
>
> Key: CASSANDRA-2009
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2009
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Trivial
> Fix For: 0.7.1
>
> Attachments:
> 0001-Move-and-rename-byteBufferToInt-and-toByteBuffer-int.patch,
> 0002-Move-method-to-read-a-BB-in-BBUtil-an-rename-to-matc.patch,
> 0003-Move-inputStream-to-BBUtil-and-change-clone-to-dupli.patch,
> 0004-Move-bytesToHex-BB-to-BBUtil-and-create-BBUtil.hexTo.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> A number of methods are in FBUtilities while they more naturally belong to
> ByteBufferUtil. Moreover, their naming convention conflict with some of the
> method already moved to ByteBufferUtil.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
