You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/18 17:07:32 UTC
[jira] [Commented] (BEAM-1051) Extend the TestSparkRunner with its
own TransformTranslator containing test evaluators
[ https://issues.apache.org/jira/browse/BEAM-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179936#comment-17179936 ]
Beam JIRA Bot commented on BEAM-1051:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> Extend the TestSparkRunner with its own TransformTranslator containing test evaluators
> --------------------------------------------------------------------------------------
>
> Key: BEAM-1051
> URL: https://issues.apache.org/jira/browse/BEAM-1051
> Project: Beam
> Issue Type: Improvement
> Components: runner-spark
> Reporter: Jean-Baptiste Onofré
> Priority: P2
> Labels: stale-P2
>
> When we have to test low level features in the Spark runner, requiring access to the {{RDDs}} or {{DStreams}}, we have to create a "fake" {{PTransform}} with a custom evaluators in the core Spark runner.
> In order to avoid to pollute the core runner, this should be done in {{TestSparkRunner}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)