Update dev env documentation to reflect pinned rust version

[Jefffrey]

I'm using helix, and the lsp integration wasn't working since it was trying to use the rust-analyzer component from the pinned toolchain, whilst I apparently only had rust-analyzer for latest toolchain.

Let me know if there's a better solution for this 🙂

Related: #14655

Update the documentation to reflect this edge case instead of requiring this new component for all CI runs

[alamb]

Thanks @Jefffrey -- this will cause all installations of DataFusion to download rust-analyzer, right? Even if it is just CI?

Does it work if you manually install rust-analyzer into the appropriate toolchain, like

rustup component add --toolchain 1.88 rust-analyzer

?

[Jefffrey]

Thanks @Jefffrey -- this will cause all installations of DataFusion to download rust-analyzer, right? Even if it is just CI?

Does it work if you manually install rust-analyzer into the appropriate toolchain, like

rustup component add --toolchain 1.88 rust-analyzer

?

Yeah that would work, but I'm mainly thinking about people who might clone datafusion for the first time, they could run into a similar issue. Maybe it would be better to handle this via a documentation update?

[alamb]

Yeah that would work, but I'm mainly thinking about people who might clone datafusion for the first time, they could run into a similar issue. Maybe it would be better to handle this via a documentation update?

Updating the guide
https://datafusion.apache.org/contributor-guide/development_environment.html

would make a lot of sense to me

[Jefffrey]

Yeah that would work, but I'm mainly thinking about people who might clone datafusion for the first time, they could run into a similar issue. Maybe it would be better to handle this via a documentation update?

Updating the guide https://datafusion.apache.org/contributor-guide/development_environment.html

would make a lot of sense to me

I've amended the documentation to reflect this 👍

[alamb]

Thank you @Jefffrey

[alamb]

❤️