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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482966#comment-16482966 ] 

ASF GitHub Bot commented on IGNITE-8406:
----------------------------------------

GitHub user 1vanan opened a pull request:

    https://github.com/apache/ignite/pull/4043

    IGNITE-8406

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/1vanan/ignite IGNITE-8406

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4043.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4043
    
----
commit d87793b407fe0f559a15871586961e0b33071733
Author: Fedotov <va...@...>
Date:   2018-05-08T09:21:05Z

    change javaDoc in IgniteDataStreamer

----


> 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)