rfc: add engine version 2 placeholder - #711
azimafroozeh wants to merge 1 commit into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 463fae4e02
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## Rollout | ||
|
|
||
| Merge as `draft`. `implementation` tracks the component table only. |
There was a problem hiding this comment.
When a component RFC lands before its code, this instruction makes RFC 0067's implementation status advance merely because a table cell changed, so the canonical registry can report engine-v2 implementation progress—or even completion—while every component remains unimplemented. Keep this parent at n/a if it is only an index, or derive its implementation state from shipped component work rather than proposal bookkeeping.
AGENTS.md reference: AGENTS.md:L3-L5
Useful? React with 👍 / 👎.
RFC 0048 keeps the staged retrieval algebra. The lexical contract moves to 2026-09-18-analyzed-lexical-search (`@analyzed`, analyzer profiles, `terms`, `match_terms`, `bm25_v1`, the exact scan baseline, the regression cases); the grammar rules, capability matrix, C1–C4 and cross-type discovery move to 2026-09-18-gq-composition-and-language-evolution. Sections move verbatim; links are repointed and the evidence branch is cited by commit. Decisions recorded on the way: - The legacy spellings (`fuzzy`, `search`, `match_text`, `nearest`, retrieval in `order`, positional `rrf`) get a one-release deprecation window with a fixed mapping instead of a hard removal, following the compatibility-surfaces RFC; stored queries are re-parsed at boot. - The read options (`coverage`, `require_replay`, limits) are session settings after #742 landed `Session`, not a new request field. - The resource ledger and the DataFusion lowering sections are marked as requirements handed to the engine version 2 components named by RFC 0067 (PR #711); RFC 0048 no longer decides a planner or an admission mechanism. - RFC 0047 replaces the `full_text_search_unindexed` warning with a compile-time `T27` refusal of undeclared full-text targets and a plan-time `FullTextIndexRequired` refusal of unbuilt indexes (the RFC 0043 fence shape); a warning left invariant 7 open.
RFC 0048 keeps the staged retrieval algebra. The lexical contract moves to 2026-09-18-analyzed-lexical-search (`@analyzed`, analyzer profiles, `terms`, `match_terms`, `bm25_v1`, the exact scan baseline, the regression cases); the grammar rules, capability matrix, C1–C4 and cross-type discovery move to 2026-09-18-gq-composition-and-language-evolution. Sections move verbatim; links are repointed and the evidence branch is cited by commit. Decisions recorded on the way: - The legacy spellings (`fuzzy`, `search`, `match_text`, `nearest`, retrieval in `order`, positional `rrf`) get a one-release deprecation window with a fixed mapping instead of a hard removal, following the compatibility-surfaces RFC; stored queries are re-parsed at boot. - The read options (`coverage`, `require_replay`, limits) are session settings after #742 landed `Session`, not a new request field. - The resource ledger and the DataFusion lowering sections are marked as requirements handed to the engine version 2 components named by RFC 0067 (PR #711); RFC 0048 no longer decides a planner or an admission mechanism. - RFC 0047 replaces the `full_text_search_unindexed` warning with a compile-time `T27` refusal of undeclared full-text targets and a plan-time `FullTextIndexRequired` refusal of unbuilt indexes (the RFC 0043 fence shape); a warning left invariant 7 open.
1 participant
What & why
This PR adds RFC 0067, a placeholder that names engine version 2 as a list of components so that each component's own RFC has one parent to cite.
Backing issue / RFC
Checklist
Local verification
python3 scripts/check-docs.py— OK, 139 filescargo test --workspace— not run: no Rust files changedNotes for reviewers
draft;implementation: not-startedtracks the component table only.