Hi,
I like this ("Arrow C++ execution engine") or "Arrow C++
Executor" rather than "ACE"/"Arrow C++ Engine"/"Arrow C++
Compute Engine".
I think that we don't need an acronym because we don't have
an acronym for existing "Arrow C++ Dataset" and "Arrow C++
Filesystem". And it may confuse us and users.
Thanks,
--
kou
In <635e120f-d58f-93bb-2b4f-51525ae16...@python.org>
"Re: [DISCUSS] "Naming" the Arrow C++ execution engine subproject?" on Tue,
29 Mar 2022 00:31:18 +0200,
Antoine Pitrou <anto...@python.org> wrote:
>
> ACE is already the name of a well-known C++ library, though I'm not
> sure how widely used it is nowadays :
> http://www.dre.vanderbilt.edu/~schmidt/ACE.html
>
> I would name it "execution engine" or "Arrow C++ execution engine" in
> full.
>
> Regards
>
> Antoine.
>
>
> Le 29/03/2022 à 00:15, Wes McKinney a écrit :
>> hi all,
>> There has been a steady stream of work over the last year and a half
>> or so to create a set of query engine building blocks in C++ to
>> evaluate queries against Arrow Datasets and input streams, which can
>> be of use to applications that are already building on top of the
>> Arrow C++ project. This effort has a smaller surface area than
>> DataFusion since SQL parsing and query optimization are being left to
>> other tools.
>> I thought it would be useful to have a name for this subproject
>> similar to how we have Gandiva, Plasma, DataFusion, and other named
>> Apache Arrow subprojects. We had discussed creating a project like
>> this a few years ago [1], but since there are now multiple
>> Arrow-native or Arrow-compatible query engines in the wild, it would
>> be helpful to disambiguate.
>> One simple name is ACE — Arrow C++ Engine. I'm not very good at
>> naming
>> things, so if there are other suggestions from the community I would
>> love to hear them!
>> Thanks,
>> Wes
>> [1]:
>> https://docs.google.com/document/d/10RoUZmiMQRi_J1FcPeVAUAMJ6d_ZuiEbaM2Y33sNPu4/edit#heading=h.2k6k5a4y9b8y
