You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2016/01/20 20:56:39 UTC
[jira] [Resolved] (ACCUMULO-4113) Fix incorrect usage of ByteBuffer
[ https://issues.apache.org/jira/browse/ACCUMULO-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Turner resolved ACCUMULO-4113.
------------------------------------
Resolution: Fixed
> Fix incorrect usage of ByteBuffer
> ---------------------------------
>
> Key: ACCUMULO-4113
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4113
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.6.4, 1.7.0
> Reporter: Keith Turner
> Assignee: Keith Turner
> Priority: Critical
> Fix For: 1.6.5, 1.7.1, 1.8.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> While working on ACCUMULO-4098 I found one place where ByteBuffer was being used incorrectly. Looking around the code, I have found other places that are using ByteBuffer incorrectly. Some of the problems I found are as follows :
> * Calling {{ByteBuffer.array()}} without calling {{ByteBuffer.hasArray()}}.
> * Using {{ByteBuffer.position()}} or {{ByteBuffer.limit()}} without adding {{ByteBuffer.arrayOffset()}} when dealing with an array returned by {{ByteBuffer.array()}}.
> * Using {{ByteBuffer.arrayOffset()}} without adding {{ByteBuffer.position()}} when dealing with an array returned by {{ByteBuffer.array()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)