[
https://issues.apache.org/jira/browse/IGNITE-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-3138:
--------------------------------
Description:
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 are not called in case of
error. This must be fixed. So that the user is able to write a custom logic
around this issue.
was:
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;
- give an ability to register a callback that will be executed in case of error
so that the user code can decide whether it makes sense to proceed with the
streaming or not.
> 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
>
> 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 are not called in case of
> error. This must be fixed. So that the user is able to write a custom logic
> around this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
