The goal of the Velox and Acero open source development teams is to enable users to choose whichever execution engine offers the functionality and performance they need. Our shared vision is that these two engines (and other tooling around them, including user APIs and storage systems) should be highly modular, so that users can pick and choose components and have them all interoperate. We aim to achieve this interoperability through the Arrow and Substrait standards. There is work underway now to achieve this, by building more Arrow and Substrait integrations and by evolving the Arrow and Substrait standards to accommodate more needs.
Can we replace Arrow Compute Engine (Acero) with Velox ?
The goal of the Velox and Acero open source development teams is to enable users to choose whichever execution engine offers the functionality and performance they need. Our shared vision is that these two engines (and other tooling around them, including user APIs and storage systems) should be highly modular, so that users can pick and choose components and have them all interoperate. We aim to achieve this interoperability through the Arrow and Substrait standards. There is work underway now to achieve this, by building more Arrow and Substrait integrations and by evolving the Arrow and Substrait standards to accommodate more needs.
@@iancook1361 where to find those slides. Thanks