[
https://issues.apache.org/jira/browse/BEAM-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553379#comment-15553379
]
Kenneth Knowles commented on BEAM-726:
--------------------------------------
I've toyed with the idea that that API on this thing is the "Job API" when
discussed at the same high level of granularity as the "Runner API" and "Fn
API". I like Job, and I feel that the methods on the API support the name. (vs
generic "Result" where "Runner" actually just means "arbitrary function
Pipeline -> ResultT" - I don't think that design is as useful)
> Standardize naming of PipelineResult objects
> --------------------------------------------
>
> Key: BEAM-726
> URL: https://issues.apache.org/jira/browse/BEAM-726
> Project: Beam
> Issue Type: Bug
> Components: beam-model
> Reporter: Ben Chambers
> Assignee: Frances Perry
> Priority: Minor
>
> Today:
> PipelineResult is an interface returned by running a pipeline.
> DataflowPipelineJob is the Dataflow implementation of that interface
> FlinkRunnerResult is the Flink implementation
> EvaluationContext is the Spark implementation
> DirectPipelineResult is the DirectRunner implementation
> Ideally, all the names would indicate that they are a PipelineResult, like
> the DirectRunner does.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
