[
https://issues.apache.org/jira/browse/ARROW-16632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541066#comment-17541066
]
Weston Pace commented on ARROW-16632:
-------------------------------------
This is a good outline.
> 2 Acero's current state
Acero's public API probably has a good surface area reaching semi-stable (e.g.
everything we use for TPC-H) but there are still a few changes planned.
Acero's internal API (for exec node developers) is still a bit experimental.
There are some significant changes that are going to be made to the scheduler,
etc.
> 2.3 In PyArrow, used as a backend for datasets
I'm not sure what the question mark is here for but this is a correct statement
and would be good to mention. I think Pyarrow is also adding more and more
dplyr-like functionality built on top of datasets.
> [Website] Announce Acero Engine
> -------------------------------
>
> Key: ARROW-16632
> URL: https://issues.apache.org/jira/browse/ARROW-16632
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Website
> Reporter: Will Jones
> Priority: Major
>
> Given consensus on Acero as the name for C++ streaming execution engine, it
> may be time to write a blog post announcing the engine, how it's currently
> available in the ecosystem, and what's happening next with it.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
