Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update tokio requirement to 1.28 #7324

Merged
merged 1 commit into from Aug 18, 2023
Merged

chore(deps): update tokio requirement to 1.28 #7324

merged 1 commit into from Aug 18, 2023

Conversation

jonahgao
Copy link
Member

Which issue does this PR close?

Discussed in #7253

Rationale for this change

We are using a new API JoinSet::spawn_blocking introduced in tokio 1.28.
https://github.com/apache/arrow-datafusion/blob/f2c0100a5a10bf3ea166a1a590d94b8c9b6cf673/datafusion/core/src/physical_plan/stream.rs#L97

tokio v1.28 changelog:

1.28.0 (April 25th, 2023)
Added
task: add JoinSet::spawn_blocking and JoinSet::spawn_blocking_on (tokio-rs/tokio#5612)

So it’s better for us to raise the minimum required tokio version to 1.28.
This can help avoid compilation failures for users.

What changes are included in this PR?

Bump tokio version

Are these changes tested?

N/A

Are there any user-facing changes?

No

@github-actions github-actions bot added the core Core datafusion crate label Aug 18, 2023
@Dandandan Dandandan merged commit b9ae8de into apache:main Aug 18, 2023
21 checks passed
@Dandandan
Copy link
Contributor

Thanks @jonahgao

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Core datafusion crate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants