Hi, Yes, Avro release includes all modules/artifacts for now (we are discussing about individual releases per language).
Regards JB On Thu, Jun 20, 2024 at 8:57 AM Xuanwo <xua...@apache.org> wrote: > > Hi, JB > > I'm not familiar with the Avro community. Do they release all packages > including rust together, or do they release them separately? > > I have noticed that current apache-avro's version is v0.16.0 and the next one > will be v0.17.0? > > On Thu, Jun 20, 2024, at 14:52, Jean-Baptiste Onofré wrote: > > Hi Renjie > > > > As discussed together, we are working on Avro 1.11.4 and 1.12.0 > > releases. We are pretty close now, I think we can reasonably plan the > > releases to vote next week. > > > > I will keep you posted about that. > > > > Regards > > JB > > > > On Thu, Jun 20, 2024 at 8:37 AM Renjie Liu <liurenjie2...@gmail.com> wrote: > >> > >> Hi, all: > >> > >>> we just have to make sure that we're not able to write metadata without > >>> field-IDs because that would violate the spec (and cause potentially > >>> compatibility issues down the road). > >> > >> > >> We need to wait for a while for the avro community's release to fix it, > >> but it's not expected to be too long. > >> > >> We can move on with other things first, such as updating documentation. > >> > >> On Thu, Jun 20, 2024 at 4:39 AM Fokko Driesprong <fo...@apache.org> wrote: > >>> > >>> +1 all in for a release looking at the amount of great features that are > >>> staged. > >>> > >>> Thank you Renjie and Xuanwo for attending the community sync, especially > >>> looking at your time zone. Renjie raised the issue of not having > >>> field-IDs based resolution when reading Avro. I think we're fine for > >>> leaving that out for the next release, we just have to make sure that > >>> we're not able to write metadata without field-IDs because that would > >>> violate the spec (and cause potentially compatibility issues down the > >>> road). > >>> > >>> Kind regards, > >>> Fokko > >>> > >>> Op za 15 jun 2024 om 16:05 schreef NOTME ZE <st810918...@gmail.com>: > >>>> > >>>> +1 for 0.3. I think there is great progress for read support and it's > >>>> good to get some feedback now. > >>>> > >>>> lanhe...@googlemail.com.INVALID <lanhe...@googlemail.com.invalid> > >>>> 于2024年6月15日周六 18:55写道： > >>>>> > >>>>> +1 for 0.3 Release. I think it will be good for the project to show its > >>>>> progress and get some feedback. > >>>>> > >>>>> Best regards > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> Von meinem Telefon gesendet > >>>>> > >>>>> > >>>>> -------- Ursprüngliche Nachricht -------- > >>>>> Von: Xuanwo <xua...@apache.org> > >>>>> Datum: Sa., 15. Juni 2024, 12:41 > >>>>> An: dev@iceberg.apache.org > >>>>> Betreff: Re: [DISCUSSION] Preparing the Apache iceberg-rust 0.3.0 > >>>>> release > >>>>> > >>>>> There are bunch of works before catching up java implementation. But > >>>>> build a rapid feedback loop is importance for our project. > >>>>> > >>>>> I support cutting a 0.3 release now 🤩 > >>>>> > >>>>> On Sat, Jun 15, 2024, at 18:34, Renjie Liu wrote: > >>>>> > >>>>> Hi, everyone: > >>>>> > >>>>> The iceberg-rust project has landed more features since last release, > >>>>> and I propose to do 0.3.0 release. This release mainly focuses on read > >>>>> support, including following features: > >>>>> > >>>>> 1. Expression system. > >>>>> 2. File base task planning. > >>>>> 3. Manifest file pruning. > >>>>> 4. Datafile pruning. > >>>>> 5. Reading into arrow record batches. > >>>>> 6. Glue, hive catalog supported, without supporting updates. > >>>>> 6. Several improvements to the rest catalog. > >>>>> > >>>>> I'm happy to volunteer to be the release manager for iceberg-rust 0.3.0. > >>>>> > >>>>> Welcome to join the discussion and share your thoughts! > >>>>> > >>>>> Xuanwo > >>>>> > > -- > Xuanwo
