u70b3 commented on issue #66497: URL: https://github.com/apache/doris/issues/66497#issuecomment-5279535778
@Gabriel39 friendly ping 🙂 When you have a moment, could you take a look at the v5 design above (the revised publication candidate posted on Aug 10)? It was rewritten specifically to pin down the three correctness issues from your round-5 review: 1. `OUTCOME_UNKNOWN` keeps the same-name serialization fence (including across normalization-version upgrades) until an audited force release — `RESOLVE LANCE INDEX JOB ... AS FORCE_RELEASE` requires a non-empty risk-acceptance note, so a late commit from an old executor can no longer slip through silently. 2. Mutation attribution and metadata refresh are now independent, durable decisions — e.g. a `CommitConflict` after invocation ends the job as `NOT_COMMITTED` but still requires an authoritative refresh, and `IF [NOT] EXISTS` resolves the race window by comparing authoritative readable fields. 3. Operator resolution is now a fully specified durable state transition: explicit `RESOLVE LANCE INDEX JOB` SQL, privilege requirements, persisted `LastResolvedBy`/`LastResolvedAt`, bounded immutable resolution events, and defined replay behavior — without claiming the original mutation outcome became known. The implementation constraints are pinned as well: native mutation runs in a hard-limited worker process (never in FE/BE), `file://` mutation is a separate disabled-by-default operator assertion with topology checks, and REST goes through one code-defined `generic-read-only-v1` profile with provider mutation profiles explicitly future work. I also posted a small implementation errata today as a comment above — logical/physical index-type vocabulary normalization (case/underscore-insensitive, umbrella `VECTOR` family accepted), INCONSISTENT results keep the `READ_FAILED` token, reserved system-index entries (`__lance_frag_reuse`/`__lance_mem_wal`) are filtered, and the physical-inspection TVF shares the 256-char name cap — recorded as comments rather than a v6 since none of these change the design semantics. Implementation has started in stages per @zhangstar333's suggestion — the first PR (#66637, read-only `SHOW INDEX`) is open — so your review or approval of v5 would unblock the next stages. Thanks! -- 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]
