[
https://issues.apache.org/jira/browse/FLINK-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15611349#comment-15611349
]
ASF GitHub Bot commented on FLINK-4894:
---------------------------------------
Github user uce commented on the issue:
https://github.com/apache/flink/pull/2690
That is tested in the record serializer tests and now also in the added
writer test.
In general, the record writer and serializer are very tightly coupled and
confusing at times. I think it would be very good to do some refactorings here
-- at a later time though.
> Don't block on buffer request after broadcastEvent
> ---------------------------------------------------
>
> Key: FLINK-4894
> URL: https://issues.apache.org/jira/browse/FLINK-4894
> Project: Flink
> Issue Type: Improvement
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
>
> After broadcasting an event (like the checkpoint barrier), the record writer
> might block on a buffer request although that buffer will only be needed on
> the next write on that channel.
> Instead of assuming that each serializer has a buffer set, we can change the
> logic in the writer to request the buffer when it requires one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
