You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iceberg.apache.org by Ian Streeter <ia...@snowplowanalytics.com> on 2026/01/12 13:40:52 UTC

REST spec change to allow 404 on config endpoint

Hi all,

My colleague has submitted a PR which proposes a small change to the REST
catalog spec:

https://github.com/apache/iceberg/pull/14965

It is a small change to the spec, which just explicitly allows 404 as a
possible status code on the /v1/config endpoint if the specified warehouse
does not exist.  We have observed REST catalogs returning 404 in this
scenario, so this change is just formalizing what is already happening out
there in the wild.

Does anyone have thoughts or concerns about adding this to the spec?  I
know spec changes require some scrutiny, but this one seems quite sensible.

It will help us if this PR can be merged, because of how our application
handles exceptions from Iceberg.

Thanks
Ian

-- 
*Ian Streeter*
Engineering
Snowplow Analytics <https://snowplowanalytics.com/>

Re: REST spec change to allow 404 on config endpoint

Posted by Kevin Liu <ke...@apache.org>.
Thanks for the proposal and PR. I think this is a reasonable addition to
provide more information to the clients. Note that the spec change also
adds a new error type,  `NoSuchWarehouseException`.

Spec changes require their own vote, as described in
https://iceberg.apache.org/contribute/#merging-pull-requests
Let's hear what others think before raising a vote.

Best,
Kevin Liu



On Mon, Jan 12, 2026 at 5:42 AM Ian Streeter <ia...@snowplowanalytics.com>
wrote:

>
> Hi all,
>
> My colleague has submitted a PR which proposes a small change to the REST
> catalog spec:
>
> https://github.com/apache/iceberg/pull/14965
>
> It is a small change to the spec, which just explicitly allows 404 as a
> possible status code on the /v1/config endpoint if the specified warehouse
> does not exist.  We have observed REST catalogs returning 404 in this
> scenario, so this change is just formalizing what is already happening out
> there in the wild.
>
> Does anyone have thoughts or concerns about adding this to the spec?  I
> know spec changes require some scrutiny, but this one seems quite sensible.
>
> It will help us if this PR can be merged, because of how our application
> handles exceptions from Iceberg.
>
> Thanks
> Ian
>
> --
> *Ian Streeter*
> Engineering
> Snowplow Analytics <https://snowplowanalytics.com/>
>