Update to Arrow 58

[gotocoding-DB]

Hey Lance maintainers!
I carefully searched through existing PRs and issues, but I didn't find anything related.
Is there any ongoing work to support Arrow 58?
For context: Last time, when updating to Arrow 57, a lot of work was done by @timsaucer – #5291.

If not, can we please update Lance to Arrow 58?

[wjones127]

In order to upgrade Arrow versions, we need to have other dependencies also upgrade. So the following need to upgrade:

• DataFusion (still on 57)
• Geoarrow

So I think to upgrade Arrow we'll first need to get it upgraded in those upstream repos.

[timsaucer]

Right now I think these are the dependencies and their status

• DataFusion 53.0.0 in the release process Release DataFusion 53.0.0 (Feb 2026 / Mar 2026) apache/datafusion#19692
• GeoArrow 0.8.0 (not yet started)
• GeoDataFusion (depends on DataFusion 53 release and GeoArrow)
• datafusion-python (depends on DataFusion 53 release, but some prep work is already in place)

I think there are some breaking changes in arrow 58, so if you're looking to help out I think contributing a PR to update geoarrow will help get the ball rolling. Otherwise I will probably start pecking at it after we get DataFusion 53 released

[gotocoding-DB]

I see, thanks to you both for your responses!

[gotocoding-DB]

GeoArrow update to 58: geoarrow/geoarrow-rs#1425.
And just to clarify, DataFusion already uses Arrow58 in the main branch: https://github.com/apache/datafusion/blob/main/Cargo.toml#L91-L103, but we're waiting for the library release.

[niebayes]

DataFusion has released 53 recently 2 days ago.

[timsaucer]

Thanks. We still have the other deps, like datafusion-python (which I'm working on) and geodatafusion that need to update.

[timsaucer]

Datafusion-python is now released so I think we can start on this. I will put up a PR today.

[gotocoding-DB]

Thanks @timsaucer!