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

Emmanouil Gkatziouras edited comment on IGNITE-12262 at 11/10/19 7:14 PM:
--------------------------------------------------------------------------

Issue re-opened based on the dev list discussions

[http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Pub-Sub-Streamer-Implementation-tc43944.html]

[http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-tc44064.html]

 


was (Author: gkatzioura):
Issue re-opened based on the mailing list discussions

[http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Pub-Sub-Streamer-Implementation-tc43944.html]

[http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Proposal-for-Ignite-Extensions-as-a-separate-Bahir-module-or-Incubator-project-tc44064.html]

 

> Implement a Pub/Sub Data Streamer
> ---------------------------------
>
>                 Key: IGNITE-12262
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12262
>             Project: Ignite
>          Issue Type: New Feature
>          Components: streaming
>    Affects Versions: 2.7.6
>            Reporter: Emmanouil Gkatziouras
>            Assignee: Emmanouil Gkatziouras
>            Priority: Major
>
> A Pub/Sub data streamer would assist GCP users to consume data and feed them 
> into an Ignite cache.
> This data streamer will instantiate a Pub/Sub consumer endpoint,
> The user will specify and apply a StreamTransformer to the incoming Exchange 
> which shall add the result to the data streamer.
> The streamer will register as a subscriber and will listen to incoming 
> messages. 
> The same subscriber Id shall be used for all nodes.
> Only one subscriber/node will process an incoming message, instead of every 
> subscriber receiving the same message



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to