Thank you to the comments so far -- it seems like there is a growing consensus that breaking this code into its own repository would be a good idea
One question I wanted to highlight on the broader list what to name the new repository. We have a few options on the ticket: * apache/arrow-rs-object-store * apache/arrow-object-store * apache/arrow-object-store-rs Any thoughts / comments from the broader arrow community on the ticket[1] would, as always, be appreciated Andrew [1]: https://github.com/apache/arrow-rs/issues/6183 On Thu, Aug 8, 2024 at 2:18 PM Xuanwo <xua...@apache.org> wrote: > +1 non-binding > > Carries my supportive comment from the discussion here: > > Most of my contributions, both in coding and reviewing, were focused on > object_store. I feel that object_store is distinct from other arrow-related > crates. I believe it would be beneficial to move object_store and its > development process to a separate repository. > > On Fri, Aug 9, 2024, at 01:33, Edmondo Porcu wrote: > > +1. We are using it indirectly through polars and we need to extend its > > authentication support. Opening a PR on arrow-rs is probably not > desirable > > > > On Thu, Aug 8, 2024 at 1:23 PM Andrew Lamb <al...@influxdata.com> wrote: > > > >> We are having a discussion[1] about potentially splitting out the > >> `object_store` crate (whose code is currently in the arrow-rs repo but > is > >> released separately to other crates in that repo). > >> > >> Please leave your thoughts on the ticket if you would like to > participate > >> in the discussion. > >> > >> Thanks, > >> Andrew > >> > >> [1]: https://github.com/apache/arrow-rs/issues/6183 > >> > > -- > Xuanwo > > https://xuanwo.io/ >
