So in regards to the original topic question it seems like most people
prefer option 2, which is
to keep the development of FlinkML inside the project, but try to bring in
new commiters.
A lot of other interesting points have been raised here as well, and if
people are interested in
working on thi
I agree with Martin that the original topic of this thread was about how to
keep FlinkML active so that new changes will be promptly merged. The things
we want to implement is then up to the active contributors of FlinkML.
Personally, I would prefer to keep FlinkML as part of Flink's main
reposito
I think the focus of this discussion should be how we proceed not what to
do. The what comes from the committers anyway.
There are several people who like to commit, including people from the
Streamline project. Having pull requests that are older than 6 Month is not
good for any project.
The main
On Fri, Feb 12, 2016 at 9:40 AM, Simone Robutti <
simone.robu...@radicalbit.io> wrote:
> @Suneel
>
> 1) Totally agree, as I wrote before.
>
> 2)I agree that support for PMML is premature but we shouldn't underestimate
> the variety and complexity of the uses of ML models in the industry. The
> ado
@Suneel
1) Totally agree, as I wrote before.
2)I agree that support for PMML is premature but we shouldn't underestimate
the variety and complexity of the uses of ML models in the industry. The
adoption of Flink, hopefully, will grow and reach less innovative realities
where Random Forests and SV
My 2 cents as someone who's done ML over the years - having worked on Oryx
2.0 and Mahout and having used Spark MlLib (read as "had no choice due to
strict workplace enforcement") and understands well their limitations.
1. FlinkML in its present form seems like "do it like how Spark did it".
2. T
Hi
Meanwhile until FlinkML matures, it might be worth having Flink as the engine
powering H2O in a similar way Spark are doing with their Sparkling Water.
Any thoughts?
Thanks
Slim Baltagi
On Feb 12, 2016, at 7:25 AM, Theodore Vasiloudis
wrote:
> I think Simone raises some good points here.
I think Simone raises some good points here.
The truth is that FlinkML is still in its infancy and it will be hard to
compete with mllib, H2O and Graphlab in terms of features
and algorithm "coverage".
My hope has always been that the library will be focused on what Flink does
well and implement
Hi,
I agree what Theo said. Currently, only few committers spend time to review PRs
about FlinkML. But I also agree Fabian’s opinion. I would like to keep FlinkML
under main repository of Flink. I hope new committers spending time for FlinkML.
About Simone’s opinion, yes, FlinkML is still immat
Hi Theo,
thanks for starting this discussion. You are certainly right that the
development of FlinkML is stalling. On the other hand, we regularly see
people on the mailing list asking for feature.
Regarding your proposed ways to proceed:
1) I am not sure how much it would help to move FlinkML t
I will say my opinion as a person that have worked with SparkML and will be
involved soon in the development of ML solutions on Flink.
In these days I tried to track the evolution and development of FlinkML and
I see a big critical point: FlinkML looks a lot like a placeholder for
commercial purpo
Hello all,
I would like to get a conversation started on how we plan to move forward
with FlinkML.
Development on the library currently has been mostly dormant for the past 6
months,
mainly I believe because of the lack of available committers to review PRs.
Last month we got together with Till
12 matches
Mail list logo
