FrankChen021 commented on issue #13948: URL: https://github.com/apache/druid/issues/13948#issuecomment-5225519236
### SQL and MSQ migration order For the SQL portion, [PR #19909](https://github.com/apache/druid/pull/19909) is the gate. We should not move on to the subsequent SQL-module migration until PR1 has been merged. This ensures that later work builds on the migrated SQL leaf and Quidem test APIs. Planned sequence: 1. **PR 1: SQL leaf + Quidem** — [#19909](https://github.com/apache/druid/pull/19909) 2. **PR 2: SQL core + schema** — after PR1 3. **PR 3: MSQ low-level** — after PR2 4. **PR 4: MSQ integration** — after PR2; this can be developed in parallel with PR3 if there is no file overlap 5. **PR 5: MSQ shared base + exec + POM cleanup** — after both PR3 and PR4 Dependency flow: `#19909` → PR2 → (PR3 and PR4) → PR5 Each PR will be compiled locally before pushing. The affected tests, Maven Checkstyle, and applicable static checks will also be run. JUnit 4 and Hamcrest dependencies will be removed within each PR only after that PR completes the relevant source migration; a final repository-wide cleanup will follow the last migration. -- 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]
