Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/4592
---
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/4592#discussion_r149077193
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/io/network/netty/NettyMessage.java
---
@@ -67,12 +68,53 @@
//
---
Github user NicoK commented on a diff in the pull request:
https://github.com/apache/flink/pull/4592#discussion_r148212023
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/io/network/netty/NettyMessage.java
---
@@ -64,12 +65,53 @@
//
--
Github user pnowojski commented on a diff in the pull request:
https://github.com/apache/flink/pull/4592#discussion_r148203203
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/io/network/netty/NettyMessage.java
---
@@ -64,12 +65,53 @@
//
--
GitHub user NicoK opened a pull request:
https://github.com/apache/flink/pull/4592
[FLINK-7515][network] allow actual 0-length content in
NettyMessage#allocateBuffer()
## What is the purpose of the change
Previously, length "0" meant "unknown content length" but there are c
