Publically export Arrow crate from datafusion about datafusion HOT 5 CLOSED

I though that dependencies could only be declared in Cargo.toml. Or is the idea that we use pub use arrow::* in datafusion/arrow.rs, and ask people to use use datafusion::arrow::X instead of arrow::X in their crates?

Yeah, my understanding here is we'd use the latter approach of explicitly reexporting arrow. It'd still be possible for people to declare a dependency on arrow and use it directly, but the datafusion::arrow reexport would allow for people to get an appropriate version of arrow by default, rather than having to manually upgrade deps in lockstep :)

from datafusion.

I'll take this later today if no-one else wants to claim it immediately :)

from datafusion.

I though that dependencies could only be declared in Cargo.toml. Or is the idea that we use pub use arrow::* in datafusion/arrow.rs, and ask people to use use datafusion::arrow::X instead of arrow::X in their crates?

from datafusion.

Makes a lot of sense to me 👍

I think we will need to remember to bump datafusion's major whenever we bump arrow's major in Cargo.toml, as datafusions' public API will now contain arrows' public API (right?)

from datafusion.

Thank you @returnString !

from datafusion.