taiyang-li opened a new issue, #12456: URL: https://github.com/apache/gluten/issues/12456
## Background Before proposing BOLT as a supported backend in Gluten, we would like to first extract the related changes in shared modules (for example `gluten-substrait` and `gluten-core`) into a set of smaller and independent PRs. These PRs focus on extending common abstractions / interfaces that are potentially useful to backends in general, instead of binding the changes directly to a specific BOLT backend implementation. The goal is to make sure these common-layer changes can be reviewed on their own and do not change the runtime behavior of the existing Velox / CH backends. ## Why split the work this way? - It allows us to discuss and land backend-agnostic common-layer changes without introducing the full BOLT backend at the same time. - It makes it easier for the community and BOLT contributors to review whether these changes are reasonable and whether they keep existing Velox / CH backends unaffected. ## Related preparatory PRs - #12432 - #12437 - #12435 - #12433 - #12431 - #12454 ## Proposed plan 1. Review and discuss these smaller preparatory PRs in Gluten first. 2. After the common-layer preparation is in place, submit a separate PR to introduce the BOLT backend on top of the latest community code. 3. Start a new dev discussion / vote in the community to decide whether BOLT should be accepted as one of the supported Gluten backends. ## Discussion items - Are these common-layer changes reasonable and sufficiently backend-agnostic? - Are the current PR boundaries appropriate, or should some of them be merged/split differently? - What additional design notes or documentation would be helpful before moving forward with the full BOLT backend proposal? This issue is intended to track the related work items and serve as an entry point for the design / dev discussion. -- 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]
