Hi Jungtaek, I would like to get SPARK-59841 <https://issues.apache.org/jira/browse/SPARK-59841> (PR #59119 <https://github.com/apache/spark/pull/59119>) merged for Spark 4.3 to address an inconsistency between the loadTable and loadChangelog APIs.
Would it be possible to allow another 1–2 days for review and merge before proceeding with the release? Thanks! On Mon, Sep 28, 2026 at 3:54 PM Holden Karau <[email protected]> wrote: > I’m investigating a back backport I made during some fixes and hope to > have that resolved tonight, but otherwise I think we’re looking good. > > > Twitter: https://twitter.com/holdenkarau > Fight Health Insurance: https://www.fighthealthinsurance.com/ > <https://www.fighthealthinsurance.com/?q=hk_email> > Books (Learning Spark, High Performance Spark, etc.): > https://amzn.to/2MaRAG9 <https://amzn.to/2MaRAG9> > YouTube Live Streams: https://www.youtube.com/user/holdenkarau > Pronouns: she/her > > On Mon, Sep 28, 2026 at 3:52 PM Jungtaek Lim <[email protected]> > wrote: > >> Hi dev, I'm a release manager of Apache Spark 4.3.0. >> >> We failed the release candidate 1 for Apache Spark 4.3.0, and I'm trying >> to find the timing to cut the next RC. Last time I checked, there are >> ongoing blockers (myself also filed a blocker ticket) so I kept delaying to >> trigger a new RC. >> >> Since there were a couple weeks, I would like to re-check the blockers >> before moving forward. Instead of just checking the JIRA tickets, I'd love >> to collect the information from folks, who own blocker ticket(s) and the >> rationale/justification of the blocker, and what is the estimation to >> resolve it. >> >> Would you folks mind helping me to obtain the information? This will be >> very helpful to find the timing to cut RC2 rather than blindly cutting RC2 >> and seeing it fail. >> >> Thanks! >> Jungtaek Lim (HeartSaVioR) >> >
