[jira] [Commented] (IGNITE-3138) IgniteDataStreamer: failures are not shown on the streaming side

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

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

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

GitHub user vldpyatkov opened a pull request:

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

    IGNITE-3138 - IgniteDataStreamer: failures are not shown on the strea…

    …ming side

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

    $ git pull https://github.com/vldpyatkov/ignite ignite-3138

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

    https://github.com/apache/ignite/pull/913.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 #913
    
----
commit 626d281bf161917c872d54106e6f688402cc5138
Author: vd-pyatkov <vp...@gridgain.com>
Date:   2016-08-01T14:51:44Z

    IGNITE-3138 - IgniteDataStreamer: failures are not shown on the streaming side

----


> IgniteDataStreamer: failures are not shown on the streaming side
> ----------------------------------------------------------------
>
>                 Key: IGNITE-3138
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3138
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Magda
>            Assignee: Vladislav Pyatkov
>         Attachments: DataStreamerFailuresTest.java
>
>
> If an exception happens during the streaming, the side that streams the data won't printed out anything in its logs even if IGNITE_QUIET set to false.
> This makes it's inconvenient to see whether there an issue happened during the streaming or not.
> Suggested improvements:
> - print out errors that happened during the streaming on the streaming side;
> - Future that is returned from {{addData}} methods is not called in case of error. This must be fixed. So that the user is able to write a custom logic around this feature and process errors somehow.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)