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

   > I also prefer a phased approach:
   > 
   > 1. Implement the common SHOW INDEX support first.
   > 2. Then CREATE, REPLACE, and DROP INDEX for Directory Catalog.
   > 3. .....
   >    it's better to split parts of PRs
   
     Thanks, agreed. I will keep #66497 as the umbrella lifecycle issue,
     but the implementation will not be delivered as one large PR.
   
     The proposed order is:
   
     1. Common read-only `SHOW INDEX` support for Lance external tables
        first. This PR will use authoritative FE metadata reads and will
        not include mutation jobs or BE worker changes.
     2. Complete the remaining read-only inspection surfaces, such as the
        logical count and bounded UUID/version metadata, in the same phase
        or an immediate follow-up PR depending on review size.
     3. Add Directory Catalog CREATE / REPLACE / DROP through smaller,
        feature-gated PRs:
        - neutral FE command dispatch and the durable job/state model;
        - isolated BE worker and IVF_PQ end-to-end mutation;
        - BTREE/BITMAP completion, failure tests, and documentation.
   
     The cross-SDK mutation spike will gate the mutation PRs, but it will
     not block the initial SHOW INDEX work. REST mutation and incremental
     BUILD remain out of scope for 4.2.
   
     I will update the v5 implementation section to make this PR ordering
     explicit. The lifecycle design remains the umbrella contract, not a
     plan for one monolithic PR.


-- 
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