[jira] [Updated] (IGNITE-8406) Update IgniteDataStreamer.flush() javadoc
[
https://issues.apache.org/jira/browse/IGNITE-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-8406:
---
Fix Version/s: (was: 2.6)
2.7
> 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.7
>
>
> 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)
[jira] [Updated] (IGNITE-8406) Update IgniteDataStreamer.flush() javadoc
[
https://issues.apache.org/jira/browse/IGNITE-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Kuznetsov updated IGNITE-8406:
-
Description: 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. (was: 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.)
> 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. 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)
