We will first discuss whether to replace the RPC service with Akka or not.
Depending on the outcome we can discuss the issue of this vote again.
On Thu, Sep 4, 2014 at 10:50 AM, Kostas Tzoumas wrote:
> +1
>
>
>
>
> On Thu, Sep 4, 2014 at 10:30 AM, Aljoscha Krettek
> wrote:
>
> > +1
> > I think
+1
On Thu, Sep 4, 2014 at 10:30 AM, Aljoscha Krettek
wrote:
> +1
> I think it's good to outsource functionality that is not our main
> competency. Because of the origins of Flink in research we suffered a
> bit from NIH in the beginning. I'm happy to see this reduced piece by
> piece now.
>
>
+1
I think it's good to outsource functionality that is not our main
competency. Because of the origins of Flink in research we suffered a
bit from NIH in the beginning. I'm happy to see this reduced piece by
piece now.
On Thu, Sep 4, 2014 at 1:50 AM, Henry Saputra wrote:
> You can create patch t
You can create patch then ask for VOTE as needed but with a lot of
work involved I think it would be better to get some kind of agreement
of the proposed solution before continuing.
- Henry
On Wed, Sep 3, 2014 at 4:25 PM, Sebastian Schelter wrote:
> Hi Ufuk,
>
> It is up to the project where to
Hi Ufuk,
It is up to the project where to vote upfront before working on a code
change or whether to do it afterwards.
--sebastian
2014-09-03 15:55 GMT-07:00 Ufuk Celebi :
> Hey Daniel,
>
> I am sure that Till didn't try to set up the vote towards his desired
> outcome. Actually it should con
Hey Daniel,
I am sure that Till didn't try to set up the vote towards his desired
outcome. Actually it should conform to the Apache Voting Process.
Quoting from http://www.apache.org/foundation/voting.html:
"Expressing Votes: +1, 0, -1, and Fractions
The voting process in Apache may seem more t
Hi,
sorry, but I think the way this vote is set up is already biased towards
the author’s desired outcome. Two out of the three possible options
effectively lead to the switch to Scala. Moreover, the -1 option
requires the voter to explain his/her decision, the +1 option does not.
Best regar
+1
Let's make sure that the rewrite comes with additional documentation about
dev environment setup for new contributors.
On Wed, Sep 3, 2014 at 10:58 PM, Till Rohrmann wrote:
> In the wake of replacing the current proprietary RPC service with an Akka
> service, we have to rewrite the JobManag
In the wake of replacing the current proprietary RPC service with an Akka
service, we have to rewrite the JobManager and TaskManager. Akka is
implemented in Scala and offers bindings for Scala as well as Java. Since
the implementation using Scala would probably be neater and less verbose,
we would
