Is your feature request related to a problem or challenge? Please describe what you are trying to do.
However, #7670 also introduced a dependency on serde_json. As the various arrow and parquet crates are often low in the dependency stack and widely used, we are trying to avoid unnecessary dependencies
serde_json is a very helpful library for programmatically manipulating json objects, but many arrow usecases that use variant will not use this library (as the whole point of variant is to be more efficient)
Describe the solution you'd like
- I would like the
parquet-varaint crate to NOT depend on serde_json by default.
- I would like
parquet-variant to be a optional dependency -- so if people want easy / efficient serde_json conversion they can enable it
So like
# by default, does not have serde_json support
cargo test -p parquet-variant
# if the `serde_json` feature is added, now the serde_json code is available
cargo test -p parquet-variant --features=serde_json
# or also with --all-features
cargo test -p parquet-variant --all-features
Describe alternatives you've considered
Additional context
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
However, #7670 also introduced a dependency on
serde_json. As the various arrow and parquet crates are often low in the dependency stack and widely used, we are trying to avoid unnecessary dependenciesserde_jsonis a very helpful library for programmatically manipulating json objects, but many arrow usecases that use variant will not use this library (as the whole point of variant is to be more efficient)Describe the solution you'd like
parquet-varaintcrate to NOT depend onserde_jsonby default.parquet-variantto be a optional dependency -- so if people want easy / efficientserde_jsonconversion they can enable itSo like
Describe alternatives you've considered
Additional context