u70b3 commented on issue #66497:
URL: https://github.com/apache/doris/issues/66497#issuecomment-5595163744

   **PR roadmap** (tracking comment — I will keep this one edited up to date as 
PRs move)
   
   §9.1 deliberately leaves the slice→PR mapping to implementation. The table 
below is the current working split and the public legend for the PR3x labels 
used in PR descriptions. Design scope is unchanged; the mapping itself may 
shift with review.
   
   | Design slice (§9.1) | PR | Status | Contents |
   |---|---|---|---|
   | 1 | #66637 | merged | Directory-authoritative `SHOW INDEX` |
   | 2 | #66671 | merged | `lance_index_entries` TVF (physical UUID / 
dataset-version inspection) |
   | 3 | #67201 (PR3A) | open | Statically validated DDL surface; all mutations 
still rejected |
   | 3 | #67235 (PR3B) | open | Durable job model and state machine, same-name 
fence, unresolved quotas, replay |
   | 3 | #67630 (PR3C) | draft | Admission (snapshot read, schema contract, IF 
preflight), durable job creation with JobId result, `SHOW LANCE INDEX 
JOBS/JOB`, catalog DDL guard, gate config (default off) |
   | 3 | PR3D | planned | Dispatcher, thrift dispatch boundary, refresh driver, 
fake-worker fault tests |
   | 3 | PR3E | planned | `RESOLVE LANCE INDEX JOB ... AS FORCE_RELEASE`, 
bounded job retention |
   | 4 | — | planned | Hard-isolated one-shot worker, IVF_PQ tracer bullet |
   | 5 | — | planned | BTREE/BITMAP lifecycle, focused e2e query consumption, 
user documentation |
   
   All PRs target `branch-4.1`. Mutation remains disabled until the §9.2–9.6 
evidence gates pass (§9.7).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to