In my vector IO PR it was raising false positives about a new class. Maybe the process should be something like "submitter needs approval for extra exclusions"
more troublesome: once a release has shipped, those exclusions should be stripped from the master branch, as then a regression is a genuine failure On Thu, 25 Apr 2024 at 16:06, Gang Wu <ust...@gmail.com> wrote: > Let me take a look at the exclusions of japicmp. Will try to remove > them as much as possible. > > Best, > Gang > > On Thu, Apr 25, 2024 at 10:01 PM Gábor Szádovszky <ga...@apache.org> > wrote: > > > Sorry, I was not able to attend the meeting. Let me put some notes here: > > > > 2. We have been fighting with compatibility issues for a while now. > That's > > why we introduced japicmp. I can see many exclusions in the master pom. I > > think we should investigate if these exclusions cause any issues before > the > > next release. We should avoid excluding code from the compatibility > checker > > even if it seems reasonable because they tend to be kept there from > release > > to release. > > > > 3. Let's call it parquet-mr 2.0. "Parquet" might be confusing since this > > mailing list is used for both parquet-mr and parquet-format. > > I think the main requirement for parquet-mr 2.0 would be to have it > > "standalone". The core should contain an API that is able read/write > > parquet files at different levels. It should be released in a way that it > > does not bring any dependencies. (What is required should be shaded.) We > > can even start developing the new API in a separate module under > parquet-mr > > 1.x, so our clients can play with it and give feedback. > > > > Xinli shang <sha...@uber.com.invalid> ezt írta (időpont: 2024. ápr. 23., > > K, > > 16:31): > > > > > 4/23/2024 > > > > > > Attendee Fokko Driesprong, Vinoo Ganesh, Xinli Shang > > > > > > > > > Parquet-mr 1.14 release: > > > > > > 1. Fokko and Gang will discuss starting the release soon > > > > > > 2. There are a few breaking changes we need to make to ensure backward > > > compatibility and do proper testing > > > > > > 2. Vinoo will shadow and do some testing > > > > > > 3. Ideas on the release of Parquet 2.0. We start collecting thoughts > and > > > welcome everybody to share opinions. > > > -- > > > Xinli Shang > > > > > >
