[
https://issues.apache.org/jira/browse/ARROW-16632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541023#comment-17541023
]
Will Jones commented on ARROW-16632:
------------------------------------
Potential outline:
# Motivation
## Why streaming?
## Introduce the name, where codebase lives
## Where does this fit in versus other Arrow-based engines (e.g. DuckDB,
DataFusion, Velox)? (No SQL or optimizer, low-level and modular design)
# Acero's current state
## In R arrow package, used as backend for Arrow dplyr queries / Datasets
## Results can be retrieved as a Record Batch Reader, which can be passed
through Arrow's C data interface. This is used, for example, to create
pipelines that do some processing in Acero and some in DuckDB.
## In PyArrow, used as backend for datasets(?)
# Acero's near future
## Substrait support
## OpenTelemetry integration
> [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)
