Hi, Sriram,
Yes, that's the correct direction to go.
Cheers!
-Yi
On Wed, Aug 31, 2016 at 12:39 PM, Sriram Ramachandrasekaran <
sri.ram...@gmail.com> wrote:
> Thanks Jagadish.
> So, in essence, I should be looking at samza-11 branch for the final API
> against which I would have to write the Me
Thanks Jagadish.
So, in essence, I should be looking at samza-11 branch for the final API
against which I would have to write the Mesos integration pieces?
On Thu, Sep 1, 2016 at 12:56 AM, Jagadish Venkatraman <
jagadish1...@gmail.com> wrote:
> Hi Sriram,
>
> I had started prototyping it (purely
Hi Sriram,
I had started prototyping it (purely to ensure that the Samza API makes
sense with Mesos). The exact API on the Samza-11 trunk is slightly
different, but hopefully there're similarities -
https://github.com/apache/samza/blob/master/samza-core/src/main/java/org/apache/samza/clustermanage
Yi,
That's a good amount of history to know. I will take a look at 680 and then
see if I can implement something as well. If there's some stuff that's
already done, would be glad to re-use it too.
Thanks again
On Wed, Aug 31, 2016 at 10:58 PM, Yi Pan wrote:
> Hi, Sriram,
>
> The story behind del
Hi, Sriram,
The story behind delaying the integration of SAMZA-375 is that there are
tons of repeated code in SamzaAppMaster that exist in both samza-yarn and
Mesos. W/o the change we recently made in SAMZA-680, we are going to copy
the SamzaAppMaster code for every distributed execution system th
