beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davor Bonaci (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-243) Remove DirectPipelineRunner and keep only the InProcessPipelineRunner
Date Mon, 02 May 2016 16:53:12 GMT

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

Davor Bonaci commented on BEAM-243:
-----------------------------------

We absolutely should remove the old one, as soon as the new one becomes default. This is a
week or so away.

> 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)

Mime
View raw message