JB, The spec and the reference implementation are released separately so v3 and 2.0 are independent. There's no requirement that v3 is completed for Iceberg Java 2.0 and the goal of a 2.0 is to have an opportunity to deprecate and remove things so that we don't continue to carry forward and maintain older interfaces.
Ryan On Tue, Feb 20, 2024 at 1:58 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Hi Manu > > Thanks for the reminder. It sounds like a good feature and worth > discussing it :). > > It was my intention to define what we plan to include (or not) in Spec > v3 / Iceberg 2.0.0 (I sent a message about that last week). > > Regards > JB > > On Tue, Feb 20, 2024 at 10:36 AM Manu Zhang <owenzhang1...@gmail.com> > wrote: > > > > Do we still want to move forward with this feature? It's on the roadmap > for Spec V3 but it hasn't appeared in our discussion for a while. > > > > Manu > > > > On Sat, Aug 26, 2023 at 2:43 AM Mohit Garg <mohitga...@gmail.com> wrote: > >> > >> hi > >> > >> Please review the approach captured here Iceberg Table Portability This > is a continuation from the previous effort here - Support relative paths > and multiple root locations. > >> > >> -- > >> > >> kind regards > >> Mohit > -- Ryan Blue Tabular
