When we merged this into the Arrow repo, at least from my side, there was the intention to revert that maybe at some stage again. The though behind moving parquet-cpp out of the Arrow repo again was based on the idea that Parquet was one of the many interfaces Arrow does provide access to but not one of the outstanding ones. Nowadays, I have the feeling that Parquet and Arrow have a much more bound-together relationship than I initially expected. Thus we should probably accept that parquet-cpp will stay for a very long time in the Arrow repo and this should continue with the versioning.
Also we had the assumption that from time to time the parquet community would make separate releases. I have no memory anymore how we assumed that these releases would happen or why though. Basically, we had some assumptions that supported keeping the version numbers separate makes sense. All of the assumptions I can think of turned out to be false, thus keeping the version in line with Arrow (C++) makes totally sense nowadays. Uwe On Tue, Mar 9, 2021, at 7:57 PM, Micah Kornfield wrote: > I think there might have been some old agreement on this when parquet-cpp > was moved into the Arrow repo. I can't seem to find the thread, but it > would be nice for some PMC members to chime it to make sure this seems OK > to them. > > On Sat, Mar 6, 2021 at 7:38 AM Antoine Pitrou <[email protected]> wrote: > > > On Fri, 5 Mar 2021 10:26:57 -0800 > > Micah Kornfield <[email protected]> > > wrote: > > > > > > I'd like to propose that we change the default version string [1] for > > > parquet-cpp to reflect arrow releases (e.g. "parquet-cpp-arrow version > > > 3.0.0" instead of "parquet-cpp version 1.5.1-snapshot"). > > > > +1. This definitely makes the most sense. > > > > Regards > > > > Antoine. > > > > > > >
