+1 Looking forward to the critical fixes in 2.3.2.
On Thu, Jun 28, 2018 at 9:37 AM Ryan Blue wrote:
> +1
>
> On Thu, Jun 28, 2018 at 9:34 AM Xiao Li wrote:
>
>> +1. Thanks, Saisai!
>>
>> The impact of SPARK-24495 is large. We should release Spark 2.3.2 ASAP.
>>
>> Thanks,
>>
>> Xiao
>>
>> 2018
The vote passes. Thanks to all who helped with the release!
I'll start publishing everything today, and an announcement will
be sent when artifacts have propagated to the mirrors (probably
early next week).
+1 (* = binding):
- Marcelo Vanzin *
- Sean Owen *
- Felix Cheung *
- Tom Graves *
+0: No
The problem was with the changes upstream. fetch upstream and a rebase resolved
it and now the build is passing.
I also added a design doc and made the JIRA description a bit clearer
(https://issues.apache.org/jira/browse/SPARK-24020) so I hope it will get
merged soon.
Thanks,
Petar
Sean O
Hi Xiangrui,
Thanks for sending this out. I have left some comments on the google doc:
https://docs.google.com/document/d/1dFOFV3LOu6deSNd8Ndp87-wsdxQqA9cnkuj35jUlrmQ/edit#heading=h.84jotgsrp6bj
Look forward to your response.
Li
On Mon, Jun 18, 2018 at 11:33 AM, Xiangrui Meng wrote:
> Hi all,
+1. We are evaluating 2.3.1, please release Spark 2.3.2 ASAP.
Thanks,
Yucai
+1. Need to release Spark 2.3.2 ASAP
Thanks,
Venkata Ramana Gollamudi
--
Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/
-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
Yes, I'd say so.
2018-06-29 4:43 GMT+02:00 吴晓菊 :
> And it should be generic for HashJoin not only broadcast join, right?
>
>
> Chrysan Wu
> 吴晓菊
> Phone:+86 17717640807
>
>
> 2018-06-29 10:42 GMT+08:00 吴晓菊 :
>
>> Sorry for the mistake. You are right output ordering of broadcast join
>> can be the