You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Fedotov (JIRA)" <ji...@apache.org> on 2018/04/28 10:49:00 UTC

[jira] [Assigned] (IGNITE-8406) Update IgniteDataStreamer.flush() javadoc

     [ https://issues.apache.org/jira/browse/IGNITE-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Fedotov reassigned IGNITE-8406:
------------------------------------

    Assignee: Ivan Fedotov

> Update IgniteDataStreamer.flush() javadoc
> -----------------------------------------
>
>                 Key: IGNITE-8406
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8406
>             Project: Ignite
>          Issue Type: Task
>          Components: streaming
>    Affects Versions: 2.4
>            Reporter: Andrey Kuznetsov
>            Assignee: Ivan Fedotov
>            Priority: Minor
>             Fix For: 2.6
>
>
> Current {{flush()}} implementation can throw {{CacheException}} if one or more futures previously returned by {{addData()}} have been completed exceptionally. This behavior should be described in {{IgniteDataStreamer}} javadoc. Also it's worth noting explicitly that all futures completion upon return from {{flush}} does not imply all those future listeners have been completed by this moment.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)