Hello. This question is more related to the Spark development process rather than using Spark itself. The user@ mailing list is mainly for usage questions, while contribution and PR workflow discussions typically happen on the dev@ mailing list. You may get better traction there from committers and contributors who are familiar with the review process. [email protected]
So in short send a message to *[email protected] <[email protected]>* (I have already added to dev@ Reference both the JIRA issue and GitHub PR and ask if someone could review it since the reporter seems inactive. I have not checked it myself HTH Dr Mich Talebzadeh, Data Scientist | Distributed Systems (Spark) | Financial Forensics & Metadata Analytics | Transaction Reconstruction | Audit & Evidence-Based Analytics view my Linkedin profile <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> On Wed, 11 Mar 2026 at 12:00, Sergei Repnikov <[email protected]> wrote: > Hello everyone, > > I'm relatively new to contributing to Apache Spark and I've run into a > situation where I'm not sure about the proper next steps. > > I submitted a pull request (https://github.com/apache/spark/pull/54644) > a few days ago that addresses > https://issues.apache.org/jira/browse/SPARK-49634. It's a relatively > small fix that removes a config suggestion for ANSI mode, which has been > 'on' by default since 4.0.0. > > The issue is that the reporter (reviewer) assigned to the JIRA hasn't > responded either to JIRA or to the PR. Since their GitHub shows at least > 6 months of inactivity, I don't think they will respond at all. > > I plan to keep contributing to Spark in the future and want to learn the > correct etiquette for such situations. > > - The Contributing Guide says: "If a pull request has gotten little or > no attention, consider improving the description or the change itself > and ping likely reviewers again after a few days." > - I've checked the mailing list archives on "dev" and "user" for > keywords like "stalled review" or "unresponsive reporter", but I didn't > find clear guidance. > - I haven't yet pinged the "dev" list directly for a review. > > Is this the right place to ask for process advice? Or should I gently > ping the "dev" list asking for a code review? What is the generally > accepted way to handle a PR when the original reporter goes silent? > > I'd appreciate any guidance from the community on how to proceed without > breaking any protocols. > > Best regards, > Sergei Repnikov > github.com/rpnkv > > --------------------------------------------------------------------- > To unsubscribe e-mail: [email protected] > >
