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 specific exception.
I will comment directly on the PR. Thanks ! Regards JB On Wed, Jul 16, 2025 at 5:15 PM Rizzo Cascio, Fabio <fabio.rizzocas...@jpmorgan.com.invalid> wrote: > > Hi all, > > > > While working on Issue #1390<https://github.com/apache/polaris/issues/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<https://github.com/apache/polaris/pull/1989>. > > I have a couple of questions: > > 1. If multiple property updates are coming in concurrently and they don't > update the same key, should we merge the properties (entity coming in the > request and the entity refreshed) and make the update? > 2. If multiple updates are coming in concurrently and they are trying to > update the same property key value, should we throw an exception? What error > code should we return? > > I look forward to your thoughts. > > > > Thanks, > > > > Fabio > > This message is confidential and subject to terms at: > https://www.jpmorgan.com/emaildisclaimer including on confidential, > privileged or legal entity information, malicious content and monitoring of > electronic messages. If you are not the intended recipient, please delete > this message and notify the sender immediately. Any unauthorized use is > strictly prohibited.
