[
https://issues.apache.org/jira/browse/FLINK-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572977#comment-14572977
]
Till Rohrmann commented on FLINK-2116:
--------------------------------------
We could still offer a way to create matrices from a set of vectors. But then
you always have to make a tradeoff between data granularity and data
parallelism. It might be worth to make some measurements with both methods.
I guess that's the price we have to pay in order to have flexible pipelines. At
least I couldn't come up with a better/more concise solution for that.
Moreover, once we have fully specified the pipeline interface it should only be
necessary for a programmer who wants to add a new operator to simply implement
a small set of operation (in the form of implicit values). Concerning the long
type names, I think we have to weigh up how much less we want to code and how
much harder the code would be to understand/maintain then.
> Make pipeline extension require less coding
> -------------------------------------------
>
> Key: FLINK-2116
> URL: https://issues.apache.org/jira/browse/FLINK-2116
> Project: Flink
> Issue Type: Improvement
> Components: Machine Learning Library
> Reporter: Mikio Braun
> Assignee: Till Rohrmann
> Priority: Minor
>
> Right now, implementing methods from the pipelines for new types, or even
> adding new methods to pipelines requires many steps:
> 1) implementing methods for new types
> implement implicit of the corresponding class encapsulating the operation
> in the companion object
> 2) adding methods to the pipeline
> - adding a method
> - adding a trait for the operation
> - implement implicit in the companion object
> These are all objects which contain many generic parameters, so reducing the
> work would be great.
> The goal should be that you can really focus on the code to add, and have as
> little boilerplate code as possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
