You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Thomas Groh (JIRA)" <ji...@apache.org> on 2016/09/12 21:11:20 UTC

[jira] [Resolved] (BEAM-608) Set EvaluationContext once in the TransformEvaluatorFactory instead of forApplication

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

Thomas Groh resolved BEAM-608.
------------------------------
       Resolution: Fixed
    Fix Version/s: 0.3.0-incubating

https://github.com/apache/incubator-beam/pull/937

> Set EvaluationContext once in the TransformEvaluatorFactory instead of forApplication
> -------------------------------------------------------------------------------------
>
>                 Key: BEAM-608
>                 URL: https://issues.apache.org/jira/browse/BEAM-608
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-direct
>            Reporter: Thomas Groh
>            Assignee: Thomas Groh
>            Priority: Minor
>              Labels: easyfix
>             Fix For: 0.3.0-incubating
>
>
> Remove the EvaluationContext parameter from TransformEvaluatorFactory.forApplication() and move it to TransformEvaluatorRegistry.defaultRegistry(), and pass it to all of the TransformEvaluatorFactories created in that constructor.
> A single EvaluationContext is produced per pipeline run. TransformEvaluatorFactories are also produced once per pipeline run, as they are stateful (especially with regards to sources). This change will both ensure that Evaluators cannot be reused across pipelines, and cleans up the signature of the TransformEvaluatorFactory interface.



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