Hi Wenchen,
Could you please wait for https://github.com/apache/spark/pull/50246 to be
merged before you cut the next RC?
Thanks,
Huaxin
On Mon, Mar 31, 2025 at 8:53 PM Wenchen Fan wrote:
> Hi all,
>
> Thanks for your feedback! Regarding
> https://github.com/apache/spark/pull/50187 , I don't
Unsubscribe
-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
Hi all,
Thanks for your feedback! Regarding
https://github.com/apache/spark/pull/50187 , I don't think it's a 4.0
blocker as it's a CI issue for the examples module. Other than that, all
other issues have been resolved and I'll cut the next RC after
https://github.com/apache/spark/pull/50197 is me
Hi Jia,
Thanks for your detailed explanation! The existing implementation of
geospatial serialization, predicate pushdown, and other features in Apache
Sedona is indeed valuable for this project. What we’re proposing isn’t
something entirely new to the industry but rather a re-architecture: we
bel
1. mino does actually have atomic object relenames, but as it is file by
file, task commit is nonatomic;
2. v2 task commit is also unsafe -it just writes to the destination.
There is no way committer which supports task failure can be as fast as
this.
further reading
https://github.
unsubscribe
