You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2016/06/16 02:31:05 UTC

[jira] [Resolved] (BEAM-243) Remove DirectPipelineRunner and keep only the InProcessPipelineRunner

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

Kenneth Knowles resolved BEAM-243.
----------------------------------
    Resolution: Fixed

Awesome.

> Remove DirectPipelineRunner and keep only the InProcessPipelineRunner
> ---------------------------------------------------------------------
>
>                 Key: BEAM-243
>                 URL: https://issues.apache.org/jira/browse/BEAM-243
>             Project: Beam
>          Issue Type: Task
>          Components: runner-direct
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Thomas Groh
>
> We have two runners for local JVM/process: the "old" DirectPipelineRunner and the "new" InProcessPipelineRunner.
> They have different feature (for instance the DirectPipelineRunner doesn't support Unbounded PCollection, whereas InProcessPipelineRunner does).
> To avoid confusion, we could remove the "old" DirectPipelineRunner.



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