Skip to content

Track bounded simplification of parsing, output, sessions and transaction ownership #911

Description

@apstndb

Goal

Make the existing implementation simpler through bounded, independently reviewable PRs. This tracks the remaining September 2026 architecture proposals, concretized against main commit 96a8a60ab5df71447b30db1826d4da2d6677c42b. Each child specifies a chosen implementation, deletion target, behavior boundaries and validation. It is a work sequence, not permission for a broad rewrite.

Already complete

These are completed baselines and must not be implemented again. Existing #380 is reused for source preservation. #790 remains the separate BIGQUERY typed-result contract; #738 and #538 are completed background work, not reopened tasks.

Independently startable work

Work with prerequisites

Sequence and implementation boundaries

  • Export-writer inputs + explicit query-cache publication → query rendering overrides → explicit operation output. Progress stop/join also precedes explicit operation output.
  • Fixed session construction identity → candidate validation and adoption.
  • Direct pending transition + completed heartbeat investigation → stable logical transaction lifetime → automatic-DML queue ownership.
  • Source-envelope changes land before parser-mapping cleanup. Result-body migration lands before the broad explicit-output signature migration. Both orders are recorded as blocked-by links so implementations do not overlap in the shared files; these are sequencing prerequisites, not semantic contract dependencies.
  • Use separate worktrees per PR. Parallelize independent preparation; serialize heavy gates and integrate changes against refreshed main. Keep each issue's old path removal in the same PR as its replacement.

The heartbeat item is an unreproduced scheduling hypothesis with a deterministic investigation plan. It is not a confirmed bug or a reason to rewrite locking. The query-cache item identifies a source-backed behavior discrepancy and requires a red/green regression before its fix. Other items are structural refactors except the explicitly documented SOURCE/batch echo and pre-output progress improvements.

Completion criteria

  • Every child has a merged PR satisfying its own behavior and deletion criteria, or a documented evidence-based disposition for the investigation.
  • No temporary parallel representations, obsolete settings copies or ownership shims remain from this series.
  • Existing output, transaction, SET LOCAL, feature, DUMP and MCP contracts remain covered; intentional behavior changes are isolated and explained.
  • Required checks and independent current-head review are recorded per PR. No performance or correctness claims are inferred from aggregate architecture review.

No package extraction campaign, single-implementation interfaces, provider-neutral result framework, dependency upgrades, release or external-repository issue creation is included.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    refactoringtech-debtTechnical debt and code quality improvementsumbrellaParent issue tracking multiple sub-issues

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions