[
https://issues.apache.org/jira/browse/IGNITE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487999#comment-15487999
]
Saikat Maitra commented on IGNITE-3303:
---------------------------------------
[~avinogradov]
Thank you Anton for reviewing the changes.
1. I will update the files to be compatible with JDK7
2. The test failed while processing large batch of events with Timeout
exceptions. I added strict checking for each event for large batch with test
timeout of 10 secs. I will validate further and try to reproduce it in local
and Teamcity.
3. I have used static inner class for IgniteContext and passing igniteCfgFile
as param. I am changing the implementation to avoid static inner class.
4. During testing I was facing error as not every event was consumed from
IgniteSource when evtBuf was non-static. I will check it further if evtBuf can
be replaced with non-static variable.
5. Yes, the ignite instance is not the cause of the exceptions. The Ignite
instance used inside IgniteSource is the Singleton object.
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: testFlinkIgniteSourceWithLargeBatch.log
>
>
> 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)
