e.org"
, Matt Cheah , Mingyu Kim
Subject: Re: New Spark json endpoints
While we're at it, adding endpoints that get results by jobGroup (cf.
SparkContext#setJobGroup) instead of just for a single Job would also be
very useful to some of us.
On Thu, Sep 17, 2015 at 7:30 AM, Imran Rashid wr
While we're at it, adding endpoints that get results by jobGroup (cf.
SparkContext#setJobGroup) instead of just for a single Job would also be
very useful to some of us.
On Thu, Sep 17, 2015 at 7:30 AM, Imran Rashid wrote:
> Hi Kevin,
>
> I think it would be great if you added this. It never go
Hi Kevin,
I think it would be great if you added this. It never got added in the
first place b/c the original PR was already pretty bloated, and just never
got back to this. I agree with Reynold -- you shouldn't need to increase
the version for just adding new endpoints (or even adding new field
Do we need to increment the version number if it is just strict additions?
On Wed, Sep 16, 2015 at 7:10 PM, Kevin Chen wrote:
> Just wanted to bring this email up again in case there were any thoughts.
> Having all the information from the web UI accessible through a supported
> json API is ver
Just wanted to bring this email up again in case there were any thoughts.
Having all the information from the web UI accessible through a supported
json API is very important to us; are there any objections to us adding a v2
API to Spark?
Thanks!
From: Kevin Chen
Date: Friday, September 11, 20
