Re: Concurrent Namespace Update Fails with RuntimeException and 500 Error #1390

409 interpreted for an update as "already exists"... That sounds very wrong... On Fri, Aug 1, 2025 at 1:06 AM Dmitri Bourlatchkov wrote: > > Hi Robert, > > > Isn't it okay to yield a HTTP/409 in this particular case > (namespace properties) and let the user figure out the right values? > > Unfort

Re: Concurrent Namespace Update Fails with RuntimeException and 500 Error #1390

Hi Robert, > Isn't it okay to yield a HTTP/409 in this particular case (namespace properties) and let the user figure out the right values? Unfortunately, I do not think it would be ok. AFAIK, current Iceberg java code interprets 409 in this case as "namespace already exists" [1]. I'm personally

Re: Concurrent Namespace Update Fails with RuntimeException and 500 Error #1390

Having retries would be great. However, for namespace property updates, the situation is undefined, because there are no "prerequisites" that have to be satisfied. Say, you have two concurrent requests: - One requests sets a=b - Another request removes a - Yet another request sets a=c Technically

Re: Concurrent Namespace Update Fails with RuntimeException and 500 Error #1390

Heads up: PR [1989] is proceeding without retries and with 409 response codes. Please review if you have an opinion. [1989] https://github.com/apache/polaris/pull/1989 Thanks, Dmitri. On 2025/07/16 15:15:19 "Rizzo Cascio, Fabio" wrote: > Hi all, > > > > While working on Issue #1390

Re: Concurrent Namespace Update Fails with RuntimeException and 500 Error #1390

Hi Fabio I think the update of namespace entities should be specific compared to other entities, because the workflow is slightly different and can be updated "transitively". Overall PR #1989 looks good to me, but I'm not sure throwing CommitException is the best option here, I would prefer to spe

Re: Concurrent Namespace Update Fails with RuntimeException and 500 Error #1390

Hi Fabio! Thanks for starting this thread! Just to clarify my GH comments: I think we need to consider table and namespace updates separately. As far as namespace updates are concerned, my reading of the Iceberg REST Catalog API spec is that the spec does not define anything about conflicts. It

Concurrent Namespace Update Fails with RuntimeException and 500 Error #1390

Hi all, While working on Issue #1390, what initially seemed like a quick fix has turned into a more complex problem. Following Dimas-b's suggestion, I'm opening this up for a wider discussion. You can see the comments on my PR #1989