I think the main thing pending is a migration of Status APIs to use Result<T>. It's probably not a great hardship to port the implementation of these wrappers to use the Result<T> APIs
On Tue, Dec 3, 2019 at 2:54 PM Micah Kornfield <emkornfi...@gmail.com> wrote: > > Hi Wes, > Is there much maintenance needed on the wrappers? > > I'd like to see them maintained for at least one more release of Arrow > (i.e. 1.0.0). > > Thanks, > Micah > > On Tue, Dec 3, 2019 at 12:23 PM Wes McKinney <wesmck...@gmail.com> wrote: > > > About 4 months ago I migrated the Parquet C++ project to use the Arrow > > IO APIs internally rather than maintaining a whole separate set of > > virtual file APIs for Parquet-specific use. To ease transitions, we > > created wrappers for the prior file interfaces so that existing > > implementers of the old APIs would not be disrupted. > > > > To be clear, the intended migration path for developers is to port > > their implementations to use the Arrow IO APIs. The question then is > > how long to maintain the deprecated wrapper interfaces. We would > > appreciate hearing from the developers that this might affect. > > > > Thanks! > > Wes > >
