I would think any transaction concerns would live at the peripheries? e.g. the Datasets? Or at least that is where compatibility would have to be built first.
On Fri, Sep 9, 2022 at 12:01 PM Sasha Krassovsky <krassovskysa...@gmail.com> wrote: > Hi Jayjeet, > Transactions are currently out of scope for Acero - Acero is only meant to > be a query execution engine. That said, it can definitely be used as a > component for building a full database engine, which could implement its > own locking of rows while Acero executes on them. You could also check out > DuckDB, which can operate on Arrow data and also supports transactions. > > Sasha > > > 9 сент. 2022 г., в 11:54, Jayjeet Chakraborty < > jayjeetchakrabort...@gmail.com> написал(а): > > > > Hi Arrow Community, > > > > Since Acero is developing very fast into a full fledged compute engine, > are > > there plans to add transaction semantics to acero, so that it can also be > > used as a database layer over already supported storage backends ? What I > > am referring to is like a Delta Lake/Iceberg kind of interface over Acero > > in C++. Thanks. > > > > > > -- > > *Jayjeet Chakraborty* > > CS PhD student > > UC Santa Cruz > > California, USA >
