TimKotowski commented on code in PR #6472:
URL: https://github.com/apache/arrow-datafusion/pull/6472#discussion_r1208635218
##########
docs/source/user-guide/example-usage.md:
##########
@@ -81,6 +81,26 @@ async fn main() -> datafusion::error::Result<()> {
+---+--------+
```
+## Arrow Versions
+
+Many of DataFusion's public APIs use types from the
+[`arrow`](https://docs.rs/arrow/latest/arrow/) crate, so if you use
+`arrow` in your project, its version must match that used by
+DataFusion.
+
+The easiest way to ensure the versions match is to use the `arrow`
+exported by DataFusion, for example:
Review Comment:
It may be good to explain which crate versions cause this issue. When you
wrote, ` its version must match that used by
DataFusion.` this is indeed correct. But most people may check out the arrow
crate still and go for 40.0, instead of the 39.0 version that is used by
Datafusion. Would it be okay to add more transparency or example cases that
would cause that mismatched types to happen? (Which using Datafusion crate with
40.0 arrow would cause this intermingle behavior).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
