Closed kyle-mccarthy closed 2 months ago
I think you managed to file this shortly after @mightyshazam and I diagnosed this in Slack :laughing:
Use deltalake-azure ~> 0.1.3
I'm guessing I need to rev the version and release deltalake-gcp with the more correct version constraints
deltalake-gcp 0.2.2 has been pushed as well with the right version ranges.
Can you verify that your troubles have been remedied @kyle-mccarthy ?
@rtyler that seems to have fixed it! thanks!
--
Note for future readers, make sure to run cargo update
to fetch the updated crates.io index.
Environment
Delta-rs version: 0.18
Binding: Rust
Environment:
Bug
What happened:
azure
andgcp
features use differentdeltalake-core
version than one re-exported by thedeltalake
crate. This makes the azure and gcp crates use a different static registry than the re-exported registry, breaking registration of cloud provider specific factories.What you expected to happen: Same version of `deltalake-core' to be used so factories can be registered under their cloud specific schemes.
How to reproduce it: Create a fresh project and add
deltalake
v0.18 with theazure
feature enabled. Note thatcrates.io
should be used as the registry rather thangit
orpath
.More details:
deltalake v0.18.1
usesdeltalake-core v0.18.1
anddeltalake-azure v0.1.2
.deltalake-azure v0.1.2
usesdeltalake-core v0.17.3
.aws
appears to be broken entirely as enabling the feature causes the crate's build to fail.