Hi Visia and Greg,
I totally agree with you. The basic design idea behind Flink and Gelly's
API meets my personal taste well.
Marking stable API must be not easy as it looks like and I don't think I
am eligible to talk about it now : )
IMO, updating multiple datasets is essential for making
Flinkās stable API provides the frameworks (DataStream and DataSet). On top of
these frameworks Gelly provides additional models for iterative algorithms, but
there are algorithms such as Minimum Spanning Tree which do not easily map to
these models (in this instance requiring nested
On Fri, Feb 24, 2017 at 1:43 PM, Vasiliki Kalavri > wrote:
Hi Greg,
On 24 February 2017 at 18:09, Greg Hogan > wrote:
> Thanks, Vasia, for starting the discussion.
>
> I was expecting
Hi Xingcan,
thank you for your input!
On 27 February 2017 at 14:03, Xingcan Cui wrote:
> Hi Vasia and Greg,
>
> thanks for the discussion. I'd like to share my thoughts.
>
> 1) I don't think it's necessary to extend the algorithm list intentionally.
> It's just like a
Hi Greg,
On 24 February 2017 at 18:09, Greg Hogan wrote:
> Thanks, Vasia, for starting the discussion.
>
> I was expecting more changes from the recent discussion on restructuring
> the project, in particular regarding the libraries. Gelly has always
> collected algorithms
Thanks, Vasia, for starting the discussion.
I was expecting more changes from the recent discussion on restructuring
the project, in particular regarding the libraries. Gelly has always
collected algorithms and I have personally taken an algorithms-first
approach for contributions. Is that
Hello squirrels,
this is a discussion thread to organize the Gelly component development for
release 1.3 and discuss longer-term plans for the library.
I am hoping that with time-based releases, we can distribute the load for
PR reviewing and make better use of our time, and also point