[
https://issues.apache.org/jira/browse/IGNITE-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16455806#comment-16455806
]
Andrey Kuznetsov commented on IGNITE-8406:
------------------------------------------
[~syssoftsol], I still deem the scenario you describe is not a subject for
'fix'. {{flush()}} just ensures all pending operations have become completed
(this may or may not throw). Completion status of all futures of interest
should be tracked separately.
> 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
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
