Here are my notes from last night’s sync. I had to leave early, so there
may be more discussion. Others can fill in the details for those topics.
*Attendees*:
John Zhuge
Ryan Blue
Yifei Huang
Matt Cheah
Yuanjian Li
Russell Spitzer
Kevin Yu
*Topics*:
- Atomic extensions for the TableCatalog
Here is the draft announcement:
===
Plan for dropping Python 2 support
As many of you already knew, Python core development team and many utilized
Python packages like Pandas and NumPy will drop Python 2 support in or
before 2020/01/01. Apache Spark has supported both Python 2 and 3 since
Spark
I created https://issues.apache.org/jira/browse/SPARK-27884 to track the
work.
On Thu, May 30, 2019 at 2:18 AM Felix Cheung
wrote:
> We don’t usually reference a future release on website
>
> > Spark website and state that Python 2 is deprecated in Spark 3.0
>
> I suspect people will then ask
Thanks! Yuming and Gengliang are working on this.
On Thu, May 30, 2019 at 8:21 AM Sean Owen wrote:
> I might need some help figuring this out. The master Maven build has
> been failing for almost a week, and I'm having trouble diagnosing why.
> Of course, the PR builder has been fine.
>
>
>
I might need some help figuring this out. The master Maven build has
been failing for almost a week, and I'm having trouble diagnosing why.
Of course, the PR builder has been fine.
First one seems to be:
Let me put up an initial patch probably around the beginning of next week
and we can talk about the maintenance involved with it there when you have
something more concrete to look at.
Thanks,
Bobby
On Wed, May 29, 2019 at 5:04 PM Reynold Xin wrote:
> Thanks Tom.
>
> I finally had time to
We don’t usually reference a future release on website
> Spark website and state that Python 2 is deprecated in Spark 3.0
I suspect people will then ask when is Spark 3.0 coming out then. Might need to
provide some clarity on that.
From: Reynold Xin
Sent:
+1 on Xiangrui’s plan.
On Thu, May 30, 2019 at 7:55 AM shane knapp wrote:
> I don't have a good sense of the overhead of continuing to support
>> Python 2; is it large enough to consider dropping it in Spark 3.0?
>>
>> from the build/test side, it will actually be pretty easy to continue
>
