You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spark.apache.org by Renyi Xiong <re...@gmail.com> on 2016/04/02 03:59:03 UTC

RE: Declare rest of @Experimental items non-experimental if they'veexisted since 1.2.0

Thanks a lot, Sean, really appreciate your comments.

Sent from my Windows 10 phone

From: Sean Owen
Sent: Friday, April 1, 2016 12:55 PM
To: Renyi Xiong
Cc: Tathagata Das; dev
Subject: Re: Declare rest of @Experimental items non-experimental if they'veexisted since 1.2.0

The change there was just to mark the methods non-experimental. The
logic was that they'd been around for many releases without change,
and are unlikely to be changed now that they've been in the wild so
long, so already acted as if they're part of the normal stable API.

Are they important? I personally consider the approximate count
methods useful. There was some recent talk of deprecating the
approximate sum, mean methods. But they're no longer experimental and
not going away soon so I suppose they're worth supporting.

On Fri, Apr 1, 2016 at 10:10 AM, Renyi Xiong <re...@gmail.com> wrote:
> Hi Sean,
>
> We're upgrading Mobius (C# binding for Spark) in Microsoft to align with
> Spark 1.6.2 and noticed some changes in API you did in
>
> https://github.com/apache/spark/commit/6f81eae24f83df51a99d4bb2629dd7daadc01519
>
>
> mostly on APIs with Approx postfix. (still marked as experimental in pyspark
> though)
>
>
> Can you help us understand how important these APIs are?
>
>
> (in C# we don't implement experimental APIs yet. We're not so sure whether
> we should or not)
>
>
> Thanks a lot,
>
> Renyi.
>
>
>