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/10/17 21:38:58 UTC

[jira] [Commented] (BEAM-757) The SparkRunner should utilize the SDK's DoFnRunner instead of writing it's own.

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

Kenneth Knowles commented on BEAM-757:
--------------------------------------

Just a note here that I'm going to have to refactor them a bit to run {{DoFn}} directly instead of via wrapping to {{OldDoFn}}. So if there are things you see in {{DoFnRunner}} that seem like leftovers from before Beam, or other concerns, let me know.

> The SparkRunner should utilize the SDK's DoFnRunner instead of writing it's own.
> --------------------------------------------------------------------------------
>
>                 Key: BEAM-757
>                 URL: https://issues.apache.org/jira/browse/BEAM-757
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-spark
>            Reporter: Amit Sela
>            Assignee: Amit Sela
>
> The SDK now provides DoFnRunner implementations, and so to avoid maintaining against the SDK, the runner should leverage the runner API instead.



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