I have mixed feelings on this but am generally supportive. If we could do something like what Neal suggests (placing an upper limit so users of the feather packages could still get a working setup), I'd be more supportive. Generally, I'd like to see us maintain at least the read path in perpetuity.
On Tue, Jun 3, 2025 at 6:09 AM Antoine Pitrou <anto...@python.org> wrote: > > > Hello > > Arrow C++ still supports the very old file format "Feather V1" which was > designed in 2016 and is superseded by the Arrow IPC file format. (*) > > (note: "Feather V2" is a synonym for Arrow IPC to encourage users of > "Feather V1" to migrate to IPC) > > I propose that we deprecate reading and writing legacy "Feather V1" > files in Arrow C++. We could then retire the functionality in one year > or so (or perhaps we can just retire the writer and keep the reader for > a bit longer). What do you think? > > Regards > > Antoine. > > > (*) https://github.com/wesm/feather/graphs/contributors >
