[
https://issues.apache.org/jira/browse/FLINK-17393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17109093#comment-17109093
]
Jiangjie Qin commented on FLINK-17393:
--------------------------------------
[~echauchot] Sorry for the late reply. You are right. This is actually a bug,
`FutureCompletingBlockingQueue` should have a constructor taking capacity as a
parameter. I just created FLINK-17761 to track this.
> Improve the `FutureCompletingBlockingQueue` to wakeup blocking put() more
> elegantly.
> ------------------------------------------------------------------------------------
>
> Key: FLINK-17393
> URL: https://issues.apache.org/jira/browse/FLINK-17393
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Common
> Reporter: Jiangjie Qin
> Priority: Major
>
> Currently, if a {{FetchTask}} is blocking on
> {{FutureCompletingBlockingQueue.put()}}, interrupt has to be called to wake
> it up, which will result in {{InterruptedException}}. We can avoid the
> interruption by having our own implementation of {{BlockingQueue.Put()}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
