[
https://issues.apache.org/jira/browse/FLINK-14412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953516#comment-16953516
]
Zili Chen edited comment on FLINK-14412 at 10/17/19 8:42 AM:
-------------------------------------------------------------
I can see the background to move FLIP-73 {{Pipeline}} to {{flink-core}} that it
is a basic concept of Flink Job shared among modules.
[~aljoscha] I'm not quick sure if ML scope {{Pipeline}} has some unavoidable
conflict(we already distinguish many of this case by package i.e. namespace,
see also Flink Path and Hadoop Path). Although I'm ok with renaming ML scope
pipeline I don't have corresponding knowledge about a good name. {{MLPipeline}}
is not bad but possibly diverges from other ML classes like {{Estimator}} or
{{Estimator}}.
was (Author: tison):
I can see the background to move FLIP-73 {{Pipeline}} to {{flink-core}} that it
is a basic concept of Flink Job shared among modules.
[~aljoscha] I'm not quick sure if ML scope {{Pipeline}} has some unavoidable
conflict? Although I'm ok with renaming ML scope pipeline I don't have
corresponding knowledge about a good name. {{MLPipeline}} is not bad but
possibly diverges from other ML classes like {{Estimator}} or {{Estimator}}.
> Rename ML Pipeline to MLPipeline
> --------------------------------
>
> Key: FLINK-14412
> URL: https://issues.apache.org/jira/browse/FLINK-14412
> Project: Flink
> Issue Type: Bug
> Components: Library / Machine Learning
> Reporter: Aljoscha Krettek
> Priority: Major
>
> In FLINK-14290 we introduced a {{Pipeline}} interface in {{flink-core}} as
> the common interface of Flink Jobs/Pipelines. Unfortunately, this name
> clashes with {{Pipeline}} in the ML package. My suggestion is to rename
> {{Pipeline}} in the ML package to {{MLPipeline}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
