You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mnemonic.apache.org by "Wang, Gang (JIRA)" <ji...@apache.org> on 2017/06/29 06:44:00 UTC

[jira] [Commented] (MNEMONIC-292) Set initial limit for ChunkBuffers(equal to capacity)

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

Wang, Gang commented on MNEMONIC-292:
-------------------------------------

[Patch|https://github.com/NonVolatileComputing/incubator-mnemonic/commit/598883fcff55c40932c34893da4f8a9533ba3572.patch]


> Set initial limit for ChunkBuffers(equal to capacity)
> -----------------------------------------------------
>
>                 Key: MNEMONIC-292
>                 URL: https://issues.apache.org/jira/browse/MNEMONIC-292
>             Project: Mnemonic
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.9.0-incubating
>            Reporter: Johnu George
>            Assignee: Wang, Gang
>             Fix For: 0.9.0-incubating
>
>
> Capacity of chunkbuffers is set to the size specified by the user. But limit is not set by default.  However, it is safer to set limit in the constructor. (as done in java bytebuffer source) Else, user may see unexpected results.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)