There are still open concerns about the incompatibility w/ Servlet Spec
6.0, which can be a problem. That will be changed/addressed in Iceberg's
v2 REST spec. But I do not see a good reason to _introduce_ this in
Polaris APIs, knowing that it is an issue.
The other topic is "OAuth" - there is
> I do not see a reason to change public facing Polaris APIs just because
Iceberg's APIs changed/evolved.
Really? If our goal is compatibility with the Iceberg REST spec, wouldn't
Polaris APIs necessarily need to change if the Iceberg ones do?
On Fri, Mar 21, 2025 at 4:14 AM Robert Stupp wrote:
Thanks for the discussion so far!
'iceberg-rest-catalog-open-api.yaml' is declared to be a 1:1 copy of
> Iceberg's v.1.7.1 'open-api/rest-catalog-open-api.yaml', but in fact it
> has already diverged beyond just code formatting.
The iceberg-rest-catalog-open-api.yaml file should indeed be a 1:1 c
Thanks Robert for bringing this up!
I see we mentioned two problems in this thread:
1) polaris-catalog-service.yaml contains reference to all catalog APIs
including the ones for Iceberg and our Polaris specific APIs,
which could be confusing to the users or new developers.
2) Polaris specific
Hi all,
We have two copies of the Iceberg REST specification in the Polaris code
base:
* spec/iceberg-rest-catalog-open-api.yaml [1] and
* spec/polaris-catalog-service.yaml [2] - via [5] [6] [7] [8]
'iceberg-rest-catalog-open-api.yaml' is declared to be a 1:1 copy of
Iceberg's v.1.7.1 'open-
