Cargo Features
[dependencies]
deltalake-core = { version = "0.21.0", default-features = false, features = ["cdf", "datafusion", "datafusion-ext", "json", "python", "unity-experimental"] }
- default = cdf
-
The
cdf
feature is set by default wheneverdeltalake-core
is added without
somewhere in the dependency tree.default-features = false - cdf default
- datafusion datafusion-ext? = datafusion-common, datafusion-expr, datafusion-functions, datafusion-functions-aggregate, datafusion-physical-expr, datafusion-physical-plan, datafusion-proto, datafusion-sql
-
Enables datafusion ^41
Affects
data_catalog::storage
,unity::datafusion
,deltalake-core::delta_datafusion
,logstore::LogStore.object_store_url
,operations::constraints
,operations::delete
,operations::load_cdf
,operations::merge
,operations::update
,operations::write
,test_utils::datafusion
… - datafusion-ext = datafusion
- json
-
Enables json of parquet ^52
parquet:
Enable JSON APIs
- python
- unity-experimental = hyper, reqwest
-
Affects
data_catalog::client
,data_catalog::unity
…
Features from optional dependencies
In crates that don't use the dep:
syntax, optional dependencies automatically become Cargo features. These features may have been created by mistake, and this functionality may be removed in the future.
- datafusion-expr datafusion?
-
Enables datafusion-expr ^41
- datafusion-common datafusion?
-
Enables datafusion-common ^41
- datafusion-proto datafusion?
-
Enables datafusion-proto ^41
- datafusion-sql datafusion?
-
Enables datafusion-sql ^41
- datafusion-physical-expr datafusion?
-
Enables datafusion-physical-expr ^41
- datafusion-physical-plan datafusion?
-
Enables datafusion-physical-plan ^41
- datafusion-functions datafusion?
-
Enables datafusion-functions ^41
- datafusion-functions-aggregate datafusion?
- hyper unity-experimental?
-
Enables hyper ^0.14
- reqwest unity-experimental?
-
Enables reqwest ^0.11.18
Unity