You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Nico Kruber (JIRA)" <ji...@apache.org> on 2017/08/25 11:49:00 UTC

[jira] [Updated] (FLINK-7515) allow actual 0-length content in NettyMessage#allocateBuffer()

     [ https://issues.apache.org/jira/browse/FLINK-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nico Kruber updated FLINK-7515:
-------------------------------
    Issue Type: Bug  (was: Sub-task)
        Parent:     (was: FLINK-7512)

> allow actual 0-length content in NettyMessage#allocateBuffer()
> --------------------------------------------------------------
>
>                 Key: FLINK-7515
>                 URL: https://issues.apache.org/jira/browse/FLINK-7515
>             Project: Flink
>          Issue Type: Bug
>          Components: Network
>    Affects Versions: 1.4.0
>            Reporter: Nico Kruber
>            Assignee: Nico Kruber
>            Priority: Minor
>
> Previously, length {{0}} meant "unknown content length" but there are cases where the actual length is 0 and we do not need a larger buffer. Let's use {{-1}} for tagging the special case instead.



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