Re: Iceberg namespace operation behaviors

This is the public link: https://www.youtube.com/watch?v=JSN9T20eAuU -Jack On Tue, Jul 16, 2024 at 7:38 PM Manu Zhang wrote: > Hi Ajantha, > > It looks the catalog sync link is not publicly accessible. Can you check? > > Thanks, > Manu > > On Wed, Jul 17, 2024 at 12:42 AM Ajantha Bhat > wrote:

Re: Iceberg namespace operation behaviors

Hi Ajantha, It looks the catalog sync link is not publicly accessible. Can you check? Thanks, Manu On Wed, Jul 17, 2024 at 12:42 AM Ajantha Bhat wrote: > We have discussed this yesterday in the catalog sync from *44:00 to > 1:03:36* > > https://drive.google.com/file/d/1SMOlxus5C92FvW9T4LOXy8Ue

Re: Iceberg namespace operation behaviors

We have discussed this yesterday in the catalog sync from *44:00 to 1:03:36* https://drive.google.com/file/d/1SMOlxus5C92FvW9T4LOXy8Ue_9cmPLyX/view?usp=sharing&t=2643 IIRC, the conclusion was that each catalog may handle namespaces differently, with some supporting multi-level namespaces and other

Re: Iceberg namespace operation behaviors

Hi As namespace is not part of the spec, each REST server implementation can use a different logic from another one. The TCK will be able to verify the most abstract operations on namespace (common denominator on namespace behavior). Regards JB On Tue, Jul 16, 2024 at 11:11 AM Yong Zhang wrote:

Re: Iceberg namespace operation behaviors

It seems TCK will make sure the logic of the REST is consistent. So in the future iceberg will make all things align. We can merge the current PR to avoid a burden on the user. WDYT? Thanks! Yong On Thu, 11 Jul 2024 at 01:04, Ajantha Bhat wrote: > Thanks for initiating this discussion. > > I s

Re: Iceberg namespace operation behaviors

Thanks for initiating this discussion. I suggested moving it to the mailing list because the javadoc of SupportsNamespaces and the REST API spec don't clearly define how to handle missing parent namespaces. I'm generally +1 of

Re: Iceberg namespace operation behaviors

Hi, Yong: Thanks for reporting this. Do you think iceberg needs to standardize the REST spec to make sure the > logic is the same for using the SupportsNamespace interface? Yes, I think it's valuable. I remember @Jean-Baptiste Onofré had a proposal for TCK of rest catalog, and this case shows

Iceberg namespace operation behaviors

Hi all, When I was using the SupportsNamespaces to do the namespace create and exists check with other catalog services that implement the Iceberg REST API, I found it has different results with different catalog services. Iceberg has provided a standard API to do the namespace operations, but see