It depends on the release manager's decision in general, but historically
we skip the vote on old tags in favor of new RC tags.
I believe Yuming will decide as the 3.3.1 release manager.
On Tue, Oct 11, 2022 at 1:17 PM Jonathan Kelly
wrote:
> Ah, OK, I didn't realize that you were waiting for
Ah, OK, I didn't realize that you were waiting for something. Will the
v3.3.1-rc3 tag be moved once SPARK-40703 is out? (Is that even possible?)
Or will you just cut rc4 eventually and never vote on rc3?
On Tue, Oct 11, 2022 at 1:14 PM Dongjoon Hyun
wrote:
> Yes, that's the current status.
>
>
Yes, that's the current status.
FYI, 3.3.1-rc3 tag was created 6 days ago but the vote was not started
because we are waiting for
https://issues.apache.org/jira/browse/SPARK-40703
Chao Sun pinged the release manager 4 days ago and has been working on it.
Now, his PR is ready for 3.3.1 release
Yep, makes sense. Thanks for the quick response!
On Tue, Oct 11, 2022 at 12:04 PM Sean Owen wrote:
> Actually yeah that is how the release vote works by default at Apache:
> https://www.apache.org/foundation/voting.html#ReleaseVotes
>
> However I would imagine there is broad consent to just
Actually yeah that is how the release vote works by default at Apache:
https://www.apache.org/foundation/voting.html#ReleaseVotes
However I would imagine there is broad consent to just roll another RC if
there's any objection or -1. We could formally re-check the votes, as I
think the +1s would
Hi, Yuming,
In your original email, you said that the vote "passes if a majority +1 PMC
votes are cast, with a minimum of 3 +1 votes". There were four +1 votes
(all from PMC members) and one -1 (also from a PMC member), so shouldn't
the vote pass because both requirements (majority +1 and minimum
Hi everyone,
It seems that there's no rule to enforce sort order and distribution when
using "CREATE TABLE table PARTITIONED BY (...) AS (SELECT ... FROM );"
statements.
With iceberg, partitioned tables have a distribution requirement[1] and it
would be nice to have those automatically applied
More insights on config regarding this issue:
With spark.sql.adaptive.enabled set true, this fails for all 3.x
versions, except for master (3.4.0-SNAPSHOT). When set false, it works
as expected for all versions.
With spark.sql.adaptive.enabled set true, and
Hi Devs,
this has been raised by Swetha on the user mailing list, which also hit
us recently.
Here is the question again:
*Is it guaranteed that written files are sorted as stated in
**sortWithinPartitions**?*
ds.repartition($"day")
.sortWithinPartitions($"day", $"id")
.write
