Thanks, Xiao. I will close this vote within a couple of hours.
2021년 2월 26일 (금) 오후 4:30, Xiao Li 님이 작성:
> I confirmed that Q17 and Q39a/b have matching results between Spark 3.0
> and 3.1 after enabling spark.sql.legacy.statisticalAggregate. The result
> changes are expected. For more details,
I confirmed that Q17 and Q39a/b have matching results between Spark 3.0 and
3.1 after enabling spark.sql.legacy.statisticalAggregate. The result
changes are expected. For more details, you can read the PR
https://github.com/apache/spark/pull/29983/ Also, the result of Q18 is
affected by the
Since the TPC-DS performance tests are one of the main validation sources
for regressions on Spark releases maybe it is time to automate the query
outputs validation to find correctness issues eagerly (it would be also
nice to validate the performance regressions but correctness >>>
performance).
I'd roughly expect 3.2 in, say, July of this year, given the usual cadence.
No reason it couldn't be a little sooner or later. There is already some
good stuff in 3.2 and will be a good minor release in 5-6 months.
On Thu, Feb 25, 2021 at 10:57 AM Dongjoon Hyun
wrote:
> Hi, All.
>
> Since we
Nit: Java 17 -> should be available by Sept 2021 :-)
Adoption would also depend on some of our nontrivial dependencies
supporting it - it might be a stretch to get it in for Apache Spark 3.2 ?
Features:
Push based shuffle and disaggregated shuffle should also be in 3.2
Regards,
Mridul
On
Hi, All.
Since we have been preparing Apache Spark 3.2.0 in master branch since
December 2020, March seems to be a good time to share our thoughts and
aspirations on Apache Spark 3.2.
According to the progress on Apache Spark 3.1 release, Apache Spark 3.2
seems to be the last minor release of
Unsubscribe
