You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Saikat Maitra (Jira)" <ji...@apache.org> on 2019/10/20 00:38:00 UTC

[jira] [Assigned] (IGNITE-7198) Integrate with Apache Beam

     [ https://issues.apache.org/jira/browse/IGNITE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Saikat Maitra reassigned IGNITE-7198:
-------------------------------------

    Assignee: Saikat Maitra

> Integrate with Apache Beam 
> ---------------------------
>
>                 Key: IGNITE-7198
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7198
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Denis A. Magda
>            Assignee: Saikat Maitra
>            Priority: Critical
>
> Apache Beam (https://beam.apache.org/) provides a unified API for batch and streaming processing. It can be seen as a generic/portable API with multiple implementations (Spark, Flink, etc.).
> Apache Ignite perfectly fits Beam architecture as a Runner:
> https://beam.apache.org/contribute/runner-guide/
> Here is Beam's capability matrix. Let's support as much as we're capable of:
> https://beam.apache.org/documentation/runners/capability-matrix/
> Most likely the integration should go to Beam's repository:
> https://github.com/apache/beam/tree/master/runners
> Discussion on the dev list: http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-as-a-distributed-processing-back-ends-td25122.html



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