Skip to content

[TRACKING] Open PR backlog triage: verdicts for open PRs (close / convert-to-issue / keep) #19306

Description

@voonhous

Tracking issue for a full triage of the open PR backlog. All 555 open PRs as of 2026-07-16, from #2607 (2021-02-26) to #19305 (2026-07-16), were reviewed against master at e098da7 (2026-07-15) to decide what can be closed, what should be converted into an issue, and what is still viable.

The full per-PR checklists, with a one-line reason for every verdict, are in the first three comments below. Each entry has a checkbox -- tick it as the PR gets addressed (GitHub shows an x-of-y task progress bar per comment):

  • Comment 1: CLOSE (166)
  • Comment 2: CONVERT to issue, then close (166)
  • Comment 3: KEEP (223)

These verdicts are recommendations, not decisions. If you are the author or a reviewer of a PR listed under CLOSE or CONVERT and believe it should stay open, please comment here or on the PR.

Scope and method

  • Covers every open apache/hudi PR as of 2026-07-16, from [HUDI-1643] Hudi observability - framework to report stats from execu… #2607 (2021-02-26) to
    [HUDI-9666] Auto-deduce ComplexKeyGenerator single-field record-key encoding on branch-0.x #19305 (2026-07-16).
  • Every PR was assessed against master at e098da7 (2026-07-15): whether the
    touched files still exist, whether an equivalent fix or feature already landed
    (the landing PR/commit is named in the reason where found), and whether the
    subsystem has since been rewritten (1.0 timeline/FileGroupReader rewrites,
    hive-sync rewrite, removed engine version poms, etc.).
  • Branch policy used: release-0.x/1.0.x and branch-0.x are frozen -- if the fix
    also applies to master the verdict is CONVERT, otherwise CLOSE (active
    committer backports were kept case-by-case). release-1.2.0 is the active
    upcoming release branch and was judged on activity. asf-site PRs were judged
    on whether the docs change is still accurate for the current site.
    feature-branch-rfc100-unstructured-data is treated as active.
  • Recent PRs (roughly May-Jul 2026) in normal review flow default to KEEP;
    [DNM] tags were read in context (stacking/merge-gate markers vs abandoned
    experiments).

Verdicts

  • CLOSE (166): obsolete -- already landed or superseded on master, code removed or rewritten, dead target branch, or abandoned after blocking review feedback.
  • CONVERT (166): the underlying bug/feature is still relevant on current master, but the PR is too stale to rescue. File a GitHub issue capturing the scope, then close the PR.
  • KEEP (223): still viable -- applies (or nearly applies) to master, or has active author/committer engagement; worth reviewing or rebasing as-is.

Summary by year created

Year CLOSE CONVERT KEEP Total
2021 4 1 0 5
2022 25 39 1 65
2023 22 42 6 70
2024 31 24 5 60
2025 54 46 31 131
2026 30 14 180 224
Total 166 166 223 555

Borderline calls flagged during triage

These verdicts were judgment calls; a maintainer close to the area should double-check
before acting.

From the oldest 400:

From the newest 155:

Metadata

Metadata

Assignees

No one assigned

    Labels

    type:epicMulti-release roadmap tracking

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions