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

Saikat Maitra commented on IGNITE-3303:
---------------------------------------

[~avinogradov]

Hi Anton,

Thank you for your feedback.

1.  I have investigated the issue further with static stopped variable and 
noticed that the exit condition was not correctly defined for the tests. I have 
fixed it and updated the PR.

2. parallelism is set to 1 so that multiple threads do not receive and process 
same events. There is no data filtering, partitioning during receiving events 
so with parallelism count more than 1, all the threads will start processing 
the events and the following test assert fails.
{noformat} assertEquals(eventList, resultList) {noformat}

The parallelism may not be useful for the tests but will be useful in cluster 
env when join, map and reduce are used over data streams. 


3. team city report 
http://ci.ignite.apache.org/viewLog.html?buildId=358872&buildTypeId=IgniteTests_IgniteStreamers&tab=buildResultsDiv

Regards,
Saikat


> 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
>         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
(v6.3.4#6332)

Reply via email to