Dmitri Bourlatchkov

IIRC, the Iceberg-side Nessie code should already be setting `author` data... I may be mistaken, though. @ajantha-bhat : Could you double check? `ClientSideCreateNamespace` is more of a backward compatibility fixture...

Yes, I edited the above comment a bit after posting it :)

Re: the java client API, it might be worth adding an input method for `CommitMeta` to `CreateNamespaceBuilder` and similar builder. The new method can be supported only in API v2...

> So, should we also have commitMultipleOperations() to create a namespace at the client side? So, it will also handle the author and committer info. This is preferable, I believe....

Could you try with Trino 436 or later? This fix might help: https://github.com/trinodb/trino/issues/17813

@ajantha-bhat : Could you have a look, please?

Since we are talking about intelligent merge operations / content manipulation, would it make sense to support multiple parents in Nessie commits (like in git)? With a content-aware merge, I...

Well, having HTTP status code in the message still obscures its meaning. At the java client level, the actual HTTP status code is secondary to the exception class. Client interested...

I believe `BaseNessieClientServerException` do not present HTTP status in their messages, so IMHO it makes sense to align `NessieRuntimeException` sub-classes with that.

Propagating advanced properties through exceptions over REST API may be problematic in non-java language bindings and cause API divergence in those cases. We already have an existing mechanism for returning...