Hi Cheng, Thanks for flagging this. The withReplacement = true pushdown issue looks valid, but the impact seems fairly narrow. It mainly affects users doing JDBC TABLESAMPLE pushdown with withReplacement = true on PostgreSQL or Databricks. The PR also includes API changes and new TABLESAMPLE SYSTEM support, which feels more like a 4.2.1 candidate than a last-minute RC change.
Could you evaluate the risk of merging at the last minute? Otherwise I'd prefer 4.2.1, unless you think the correctness fix needs to be split out separately. Thanks, Huaxin On Mon, May 25, 2026 at 3:27 AM Cheng Pan <[email protected]> wrote: > Hi Huaxin, > > I found some issues in the implementation of JDBC connector TABLESAMPLE > pushdown, I opened SPARK-57040 and > https://github.com/apache/spark/pull/56092, it would be great if you > could take a look and evaluate whether this is a blocker and should be > included in 4.2.0 since you are the author of this feature. > > Thanks, > Cheng Pan > > > > On May 18, 2026, at 11:40, huaxin gao <[email protected]> wrote: > > Hi all, > > I plan to cut Spark 4.2.0 RC1 on May 20, assuming there are no outstanding > release blockers. > > If you have any fixes that must be included in 4.2.0, please make sure > they are merged/backported to branch-4.2 before then. If you are aware of > any release blockers, please reply with the JIRA/PR and current status. > > Thanks, > Huaxin > > >
