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

Add clobber=True when registering s3 impls #421

Merged

Conversation

gallushi
Copy link
Contributor

@gallushi gallushi commented Apr 9, 2023

fsspec recently disabled clobbering by default.

This causes an issue when importing pyathena.pandas since it tries to register an impl for s3, which already has a known impl in fsspec, so we must now explicitly pass clobber=True (the default behavior prior to the change).

@romeran
Copy link

romeran commented Apr 9, 2023

+1

@laughingman7743
Copy link
Owner

Thanks!

@laughingman7743 laughingman7743 merged commit a2e772b into laughingman7743:master Apr 9, 2023
@laughingman7743
Copy link
Owner

https://pypi.org/project/pyathena/2.24.0/
Just released v2.24.0. If necessary, I can release a patch version with this change applied to versions v2.18 through v2.23.

laughingman7743 added a commit that referenced this pull request Apr 22, 2023
Add clobber=True when registering s3 impls
laughingman7743 added a commit that referenced this pull request Apr 22, 2023
Add clobber=True when registering s3 impls
laughingman7743 added a commit that referenced this pull request Apr 22, 2023
Add clobber=True when registering s3 impls
laughingman7743 added a commit that referenced this pull request Apr 22, 2023
Add clobber=True when registering s3 impls
laughingman7743 added a commit that referenced this pull request Apr 22, 2023
Add clobber=True when registering s3 impls
laughingman7743 added a commit that referenced this pull request Apr 22, 2023
Add clobber=True when registering s3 impls
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