[
https://issues.apache.org/jira/browse/FLINK-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16233887#comment-16233887
]
ASF GitHub Bot commented on FLINK-7515:
---------------------------------------
Github user NicoK commented on the issue:
https://github.com/apache/flink/pull/4592
of course, the last change added a conflict...rebased now
> allow actual 0-length content in NettyMessage#allocateBuffer()
> --------------------------------------------------------------
>
> Key: FLINK-7515
> URL: https://issues.apache.org/jira/browse/FLINK-7515
> Project: Flink
> Issue Type: Sub-task
> 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)
