; want some more community iteration on maybe?
>>
>>
>>
>>
>>
>> --
>> View this message in context: http://apache-spark-developers
>> -list.1001551.n3.nabble.com/Python-Spark-Improvements-
>&g
e can try to use it. I think this is something that
> we
> want some more community iteration on maybe?
>
>
>
>
>
> --
> View this message in context: http://apache-spark-
> developers-list.1001551.n3.nabble.com/Python-Spark-
> Improvements-forked-from-Spark-Im
ed in converting that PR to a spark
package so that people can try to use it. I think this is something that we
want some more community iteration on maybe?
--
View this message in context:
http://apache-spark-developers-list.1001551.n3.nabble.com/Python-Spark-Improvements-forked-from-
s, progress bars, tab completion for
spark configuration properties, easier loading of scala objects via py4j.
--
View this message in context:
http://apache-spark-developers-list.1001551.n3.nabble.com/Python-Spark-Improvements-forked-from-Spark-Improvement-Proposals-tp19422p19449.html
Sent from
things here.
>
> 5. API difficulties: I agree that when coming from Python, you'd expect
> that you can do the same kinds of operations on DataFrames in Spark that
> you can with Pandas, but I personally haven't been too bothered by this.
> Maybe I'm more used to this situation from using other frame
y taste.
From: msukmanowsky [via Apache Spark Developers List]
[mailto:ml-node+s1001551n19426...@n3.nabble.com]
Sent: Thursday, October 13, 2016 3:51 AM
To: Mendelson, Assaf
Subject: Re: Python Spark Improvements (forked from Spark Improvement Proposals)
As very heavy Spark users at Parse.ly, I just wanted
is. Maybe I'm
more used to this situation from using other frameworks that have similar
concepts but incompatible implementations.
We're big fans of PySpark and are happy to provide feedback and contribute
wherever we can.
--
View this message in context:
http://apache-spark-developers-li
