Skip to content

feat(rust/core): add async traits#4014

Draft
if0ne wants to merge 1 commit into
apache:mainfrom
if0ne:rust/async
Draft

feat(rust/core): add async traits#4014
if0ne wants to merge 1 commit into
apache:mainfrom
if0ne:rust/async

Conversation

@if0ne

@if0ne if0ne commented Feb 24, 2026

Copy link
Copy Markdown
Contributor

It’s not a duplicate of #3714. It’s actually part of #3714 and adds async traits for Driver, Database, Connection, and Statement.

For now, I’ve excluded the DataFusion driver. We need a new version of DataFusion that supports arrow crates version 58.

UPD: I'm waiting for the DataFusion release with these changes: apache/datafusion#19728

@if0ne if0ne requested a review from wjones127 as a code owner February 24, 2026 08:25
@if0ne if0ne force-pushed the rust/async branch 2 times, most recently from 16075fe to aa72764 Compare February 24, 2026 09:17
@if0ne

if0ne commented Mar 2, 2026

Copy link
Copy Markdown
Contributor Author

@lidavidm @eitsupi

Should we raise the minimum supported version for the arrow crates to 58.0.0 if we want to use the async feature from arrow?

@eitsupi

eitsupi commented Mar 2, 2026

Copy link
Copy Markdown
Contributor

I suppose you want to mean apache/arrow-rs#9166.
If we use this, it seems that we will definitely need to select arrow 58.0.0 or later.

Signed-off-by: if0ne <pavel.agafonov.al@gmail.com>
@lidavidm

lidavidm commented Mar 4, 2026

Copy link
Copy Markdown
Member

Is it possible in Cargo.toml to only enforce the higher minimum version when the async feature is enabled, and leave it lower otherwise?

That said, I don't think I object in general to requiring a newer Arrow, but I'm not sure if users would find that inconvenient. I would think people try to use the newest versions where possible, so maybe it's not a big issue?

@if0ne

if0ne commented Mar 4, 2026

Copy link
Copy Markdown
Contributor Author

Is it possible in Cargo.toml to only enforce the higher minimum version when the async feature is enabled, and leave it lower otherwise?

As far as I know, it is not possible.

@if0ne if0ne marked this pull request as draft March 4, 2026 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants