[
https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611856#comment-16611856
]
Andrew Mashenkov commented on IGNITE-3303:
------------------------------------------
[~samaitra]
The fail() call in catch block will be executed in separate thread, and this
will never cause test failure with the real reason as you never call
future.get().
Instead of this test will fails with meaningless assertion "f.error() is not
null".
You can remove this fail() call and add smth like next to the end of test:
igniteSrc.stopped.set(true); // this should stop streaming gracefully.
f.get(); // this will rethrow exception in case of igniteSrc thread failure and
just waits for thread stopped otherwise.
> Apache Flink Integration - Flink source to run a continuous query against one
> or multiple caches
> ------------------------------------------------------------------------------------------------
>
> Key: IGNITE-3303
> URL: https://issues.apache.org/jira/browse/IGNITE-3303
> Project: Ignite
> Issue Type: New Feature
> Components: streaming
> Reporter: Saikat Maitra
> Assignee: Saikat Maitra
> Priority: Major
> Attachments: Screen Shot 2016-10-07 at 12.44.47 AM.png,
> testFlinkIgniteSourceWithLargeBatch.log, win7.PNG
>
>
> Apache Flink integration
> +++ *Ignite as a bidirectional Connector* +++
> As a Flink source => run a continuous query against one or multiple
> caches [4].
> Related discussion :
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Flink-lt-gt-Apache-Ignite-integration-td8163.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
