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

Roman Shtykh edited comment on IGNITE-2016 at 12/23/15 12:12 PM:
-----------------------------------------------------------------

Denis,

Thanks for your suggestions. I agree and will address them.

As for flushing, it must be safe to do it before *flush* method is called 
explicitly. It should be ok to use *IgniteDataStreamer*'s buffer, but we might 
need to have a closer look at it if we want, for instance, exactly-once 
delivery in future.


was (Author: roman_s):
Denis,

Thanks for your suggestions. I agree and will address them.

As for flushing, it must be safe to do it before *flush* method is called 
explicitly. It should be ok to use *IgniteDataStreamer*'s buffer, but we might 
need to have a closer look at it if we want exactly-once delivery in future.

> Update KafkaStreamer to fit new features introduced in Kafka 0.9
> ----------------------------------------------------------------
>
>                 Key: IGNITE-2016
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2016
>             Project: Ignite
>          Issue Type: New Feature
>          Components: streaming
>            Reporter: Roman Shtykh
>            Assignee: Roman Shtykh
>
> Particularly,
> - new consumer
> - Kafka Connect (Copycat)
> http://www.confluent.io/blog/apache-kafka-0.9-is-released
> This can be a a different integration task or a complete re-write of the 
> current implementation, considering the fact that Kafka Connect is a new 
> standard way for "large-scale, real-time data import and export for Kafka."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to