[
https://issues.apache.org/jira/browse/FLINK-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875717#comment-15875717
]
Till Rohrmann commented on FLINK-5851:
--------------------------------------
I guess for people with a Java background future makes indeed more sense.
Conceptually, I think the distinction of a future as a read only structure of a
future value and a promise as something which you can complete or break and
whose result is obtainable via a future is nice. But let's stick to the Java
terminology here.
> Renaming AsyncCollector into ResultPromise/ResultFuture
> -------------------------------------------------------
>
> Key: FLINK-5851
> URL: https://issues.apache.org/jira/browse/FLINK-5851
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Till Rohrmann
> Fix For: 1.3.0
>
>
> Currently, the async I/O API gives an {{AsyncCollector}} to an
> {{AsyncFunction}} implementation. The name does not really reflect what the
> {{AsyncCollector}} does since it does not collect but is actually a one time
> completable future. Therefore, I propose to rename the {{AsyncCollector}}
> into {{ResultPromise}} or {{ResultFuture}}. This is API changing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
