Re: [VOTE] OpenAPI: Add CatalogObjectIdentifier schema
Add my +1 vote. The vote passed with the following tally: +1: 12 (6 bindings) -1: none +0: none Thanks everyone for the review and vote. I will merge the open-api spec change. On Thu, May 14, 2026 at 10:43 PM Péter Váry wrote: > +1 > Left a small suggestion > > On Fri, May 15, 2026, 04:10 Renjie Liu wrote: > >> +1 (binding) >> >> On Fri, May 15, 2026 at 9:53 AM Daniel Weeks wrote: >> >>> +1 (binding) >>> >>> On Wed, May 13, 2026, 9:08 PM Ajantha Bhat >>> wrote: >>> +1 (non-binding) - Ajantha On Wed, May 13, 2026 at 10:32 PM Steve wrote: > +1 (non-binding) > > On Wed, May 13, 2026 at 8:44 AM Jean-Baptiste Onofré > wrote: > > > > +1 (non binding) > > > > Regards > > JB > > > > On Tue, May 12, 2026 at 10:00 PM Steven Wu > wrote: > >> > >> Hi everyone, > >> > >> I propose adding the CatalogObjectIdentifier schema to the REST > catalog OpenAPI spec. > >> PR: https://github.com/apache/iceberg/pull/16144 > >> > >> Summary: > >> > >> CatalogObjectIdentifier is an ordered list of hierarchical levels > (a JSON array of strings) that identifies any catalog object, such as a > table, view, materialized view, namespace, or function. > >> Structurally the same as Namespace; the distinct name signals "any > catalog object" rather than specifically a namespace path. > >> The kind of object an identifier refers to is determined by context > (the endpoint, or a companion type discriminator defined by that > endpoint), > not by the identifier structure itself. > >> > >> > >> Motivation: multiple concurrent efforts need a generic > catalog-object identifier and would otherwise each introduce their own > >> > >> events endpoint (#12584), > >> resolve endpoint (#15830), > >> functions endpoint (#15180). > >> > >> > >> Adding one shared schema avoids identifier proliferation as new > object types are added to the spec. > >> > >> Please review the PR and vote in the next 72 hours. > >> > >> [ ] +1 Add CatalogObjectIdentifier to the REST OpenAPI spec > >> [ ] +0 > >> [ ] -1 Do not add CatalogObjectIdentifier because... > >> > >> Only PMC members have binding votes, but other community members > are encouraged to cast non-binding votes. This vote will pass if there are > 3 binding +1 votes and more binding +1 votes than -1 votes. > >> > >> Thanks, > >> Steven > >> > >> Dev thread: > https://lists.apache.org/thread/w6r3cvj483n4fsb5js84smwg8331stbs > >> Design doc: > https://docs.google.com/document/d/1NTQhgNbP2dkIMuXUMA5JdwliVQKCp1TU_ux5J_AaPiw/edit?tab=t.0 > >> Java impl: https://github.com/apache/iceberg/pull/16160 >
Re: [VOTE] OpenAPI: Add CatalogObjectIdentifier schema
+1 Left a small suggestion On Fri, May 15, 2026, 04:10 Renjie Liu wrote: > +1 (binding) > > On Fri, May 15, 2026 at 9:53 AM Daniel Weeks wrote: > >> +1 (binding) >> >> On Wed, May 13, 2026, 9:08 PM Ajantha Bhat wrote: >> >>> +1 (non-binding) >>> >>> - Ajantha >>> >>> On Wed, May 13, 2026 at 10:32 PM Steve wrote: >>> +1 (non-binding) On Wed, May 13, 2026 at 8:44 AM Jean-Baptiste Onofré wrote: > > +1 (non binding) > > Regards > JB > > On Tue, May 12, 2026 at 10:00 PM Steven Wu wrote: >> >> Hi everyone, >> >> I propose adding the CatalogObjectIdentifier schema to the REST catalog OpenAPI spec. >> PR: https://github.com/apache/iceberg/pull/16144 >> >> Summary: >> >> CatalogObjectIdentifier is an ordered list of hierarchical levels (a JSON array of strings) that identifies any catalog object, such as a table, view, materialized view, namespace, or function. >> Structurally the same as Namespace; the distinct name signals "any catalog object" rather than specifically a namespace path. >> The kind of object an identifier refers to is determined by context (the endpoint, or a companion type discriminator defined by that endpoint), not by the identifier structure itself. >> >> >> Motivation: multiple concurrent efforts need a generic catalog-object identifier and would otherwise each introduce their own >> >> events endpoint (#12584), >> resolve endpoint (#15830), >> functions endpoint (#15180). >> >> >> Adding one shared schema avoids identifier proliferation as new object types are added to the spec. >> >> Please review the PR and vote in the next 72 hours. >> >> [ ] +1 Add CatalogObjectIdentifier to the REST OpenAPI spec >> [ ] +0 >> [ ] -1 Do not add CatalogObjectIdentifier because... >> >> Only PMC members have binding votes, but other community members are encouraged to cast non-binding votes. This vote will pass if there are 3 binding +1 votes and more binding +1 votes than -1 votes. >> >> Thanks, >> Steven >> >> Dev thread: https://lists.apache.org/thread/w6r3cvj483n4fsb5js84smwg8331stbs >> Design doc: https://docs.google.com/document/d/1NTQhgNbP2dkIMuXUMA5JdwliVQKCp1TU_ux5J_AaPiw/edit?tab=t.0 >> Java impl: https://github.com/apache/iceberg/pull/16160 >>>
Re: [VOTE] OpenAPI: Add CatalogObjectIdentifier schema
+1 (binding) On Fri, May 15, 2026 at 9:53 AM Daniel Weeks wrote: > +1 (binding) > > On Wed, May 13, 2026, 9:08 PM Ajantha Bhat wrote: > >> +1 (non-binding) >> >> - Ajantha >> >> On Wed, May 13, 2026 at 10:32 PM Steve wrote: >> >>> +1 (non-binding) >>> >>> On Wed, May 13, 2026 at 8:44 AM Jean-Baptiste Onofré >>> wrote: >>> > >>> > +1 (non binding) >>> > >>> > Regards >>> > JB >>> > >>> > On Tue, May 12, 2026 at 10:00 PM Steven Wu >>> wrote: >>> >> >>> >> Hi everyone, >>> >> >>> >> I propose adding the CatalogObjectIdentifier schema to the REST >>> catalog OpenAPI spec. >>> >> PR: https://github.com/apache/iceberg/pull/16144 >>> >> >>> >> Summary: >>> >> >>> >> CatalogObjectIdentifier is an ordered list of hierarchical levels (a >>> JSON array of strings) that identifies any catalog object, such as a table, >>> view, materialized view, namespace, or function. >>> >> Structurally the same as Namespace; the distinct name signals "any >>> catalog object" rather than specifically a namespace path. >>> >> The kind of object an identifier refers to is determined by context >>> (the endpoint, or a companion type discriminator defined by that endpoint), >>> not by the identifier structure itself. >>> >> >>> >> >>> >> Motivation: multiple concurrent efforts need a generic catalog-object >>> identifier and would otherwise each introduce their own >>> >> >>> >> events endpoint (#12584), >>> >> resolve endpoint (#15830), >>> >> functions endpoint (#15180). >>> >> >>> >> >>> >> Adding one shared schema avoids identifier proliferation as new >>> object types are added to the spec. >>> >> >>> >> Please review the PR and vote in the next 72 hours. >>> >> >>> >> [ ] +1 Add CatalogObjectIdentifier to the REST OpenAPI spec >>> >> [ ] +0 >>> >> [ ] -1 Do not add CatalogObjectIdentifier because... >>> >> >>> >> Only PMC members have binding votes, but other community members are >>> encouraged to cast non-binding votes. This vote will pass if there are 3 >>> binding +1 votes and more binding +1 votes than -1 votes. >>> >> >>> >> Thanks, >>> >> Steven >>> >> >>> >> Dev thread: >>> https://lists.apache.org/thread/w6r3cvj483n4fsb5js84smwg8331stbs >>> >> Design doc: >>> https://docs.google.com/document/d/1NTQhgNbP2dkIMuXUMA5JdwliVQKCp1TU_ux5J_AaPiw/edit?tab=t.0 >>> >> Java impl: https://github.com/apache/iceberg/pull/16160 >>> >>
Re: [VOTE] OpenAPI: Add CatalogObjectIdentifier schema
+1 (binding) On Wed, May 13, 2026, 9:08 PM Ajantha Bhat wrote: > +1 (non-binding) > > - Ajantha > > On Wed, May 13, 2026 at 10:32 PM Steve wrote: > >> +1 (non-binding) >> >> On Wed, May 13, 2026 at 8:44 AM Jean-Baptiste Onofré >> wrote: >> > >> > +1 (non binding) >> > >> > Regards >> > JB >> > >> > On Tue, May 12, 2026 at 10:00 PM Steven Wu >> wrote: >> >> >> >> Hi everyone, >> >> >> >> I propose adding the CatalogObjectIdentifier schema to the REST >> catalog OpenAPI spec. >> >> PR: https://github.com/apache/iceberg/pull/16144 >> >> >> >> Summary: >> >> >> >> CatalogObjectIdentifier is an ordered list of hierarchical levels (a >> JSON array of strings) that identifies any catalog object, such as a table, >> view, materialized view, namespace, or function. >> >> Structurally the same as Namespace; the distinct name signals "any >> catalog object" rather than specifically a namespace path. >> >> The kind of object an identifier refers to is determined by context >> (the endpoint, or a companion type discriminator defined by that endpoint), >> not by the identifier structure itself. >> >> >> >> >> >> Motivation: multiple concurrent efforts need a generic catalog-object >> identifier and would otherwise each introduce their own >> >> >> >> events endpoint (#12584), >> >> resolve endpoint (#15830), >> >> functions endpoint (#15180). >> >> >> >> >> >> Adding one shared schema avoids identifier proliferation as new object >> types are added to the spec. >> >> >> >> Please review the PR and vote in the next 72 hours. >> >> >> >> [ ] +1 Add CatalogObjectIdentifier to the REST OpenAPI spec >> >> [ ] +0 >> >> [ ] -1 Do not add CatalogObjectIdentifier because... >> >> >> >> Only PMC members have binding votes, but other community members are >> encouraged to cast non-binding votes. This vote will pass if there are 3 >> binding +1 votes and more binding +1 votes than -1 votes. >> >> >> >> Thanks, >> >> Steven >> >> >> >> Dev thread: >> https://lists.apache.org/thread/w6r3cvj483n4fsb5js84smwg8331stbs >> >> Design doc: >> https://docs.google.com/document/d/1NTQhgNbP2dkIMuXUMA5JdwliVQKCp1TU_ux5J_AaPiw/edit?tab=t.0 >> >> Java impl: https://github.com/apache/iceberg/pull/16160 >> >
Re: [VOTE] OpenAPI: Add CatalogObjectIdentifier schema
+1 (non-binding) - Ajantha On Wed, May 13, 2026 at 10:32 PM Steve wrote: > +1 (non-binding) > > On Wed, May 13, 2026 at 8:44 AM Jean-Baptiste Onofré > wrote: > > > > +1 (non binding) > > > > Regards > > JB > > > > On Tue, May 12, 2026 at 10:00 PM Steven Wu wrote: > >> > >> Hi everyone, > >> > >> I propose adding the CatalogObjectIdentifier schema to the REST catalog > OpenAPI spec. > >> PR: https://github.com/apache/iceberg/pull/16144 > >> > >> Summary: > >> > >> CatalogObjectIdentifier is an ordered list of hierarchical levels (a > JSON array of strings) that identifies any catalog object, such as a table, > view, materialized view, namespace, or function. > >> Structurally the same as Namespace; the distinct name signals "any > catalog object" rather than specifically a namespace path. > >> The kind of object an identifier refers to is determined by context > (the endpoint, or a companion type discriminator defined by that endpoint), > not by the identifier structure itself. > >> > >> > >> Motivation: multiple concurrent efforts need a generic catalog-object > identifier and would otherwise each introduce their own > >> > >> events endpoint (#12584), > >> resolve endpoint (#15830), > >> functions endpoint (#15180). > >> > >> > >> Adding one shared schema avoids identifier proliferation as new object > types are added to the spec. > >> > >> Please review the PR and vote in the next 72 hours. > >> > >> [ ] +1 Add CatalogObjectIdentifier to the REST OpenAPI spec > >> [ ] +0 > >> [ ] -1 Do not add CatalogObjectIdentifier because... > >> > >> Only PMC members have binding votes, but other community members are > encouraged to cast non-binding votes. This vote will pass if there are 3 > binding +1 votes and more binding +1 votes than -1 votes. > >> > >> Thanks, > >> Steven > >> > >> Dev thread: > https://lists.apache.org/thread/w6r3cvj483n4fsb5js84smwg8331stbs > >> Design doc: > https://docs.google.com/document/d/1NTQhgNbP2dkIMuXUMA5JdwliVQKCp1TU_ux5J_AaPiw/edit?tab=t.0 > >> Java impl: https://github.com/apache/iceberg/pull/16160 >
Re: [VOTE] OpenAPI: Add CatalogObjectIdentifier schema
+1 (non-binding) On Wed, May 13, 2026 at 8:44 AM Jean-Baptiste Onofré wrote: > > +1 (non binding) > > Regards > JB > > On Tue, May 12, 2026 at 10:00 PM Steven Wu wrote: >> >> Hi everyone, >> >> I propose adding the CatalogObjectIdentifier schema to the REST catalog >> OpenAPI spec. >> PR: https://github.com/apache/iceberg/pull/16144 >> >> Summary: >> >> CatalogObjectIdentifier is an ordered list of hierarchical levels (a JSON >> array of strings) that identifies any catalog object, such as a table, view, >> materialized view, namespace, or function. >> Structurally the same as Namespace; the distinct name signals "any catalog >> object" rather than specifically a namespace path. >> The kind of object an identifier refers to is determined by context (the >> endpoint, or a companion type discriminator defined by that endpoint), not >> by the identifier structure itself. >> >> >> Motivation: multiple concurrent efforts need a generic catalog-object >> identifier and would otherwise each introduce their own >> >> events endpoint (#12584), >> resolve endpoint (#15830), >> functions endpoint (#15180). >> >> >> Adding one shared schema avoids identifier proliferation as new object types >> are added to the spec. >> >> Please review the PR and vote in the next 72 hours. >> >> [ ] +1 Add CatalogObjectIdentifier to the REST OpenAPI spec >> [ ] +0 >> [ ] -1 Do not add CatalogObjectIdentifier because... >> >> Only PMC members have binding votes, but other community members are >> encouraged to cast non-binding votes. This vote will pass if there are 3 >> binding +1 votes and more binding +1 votes than -1 votes. >> >> Thanks, >> Steven >> >> Dev thread: https://lists.apache.org/thread/w6r3cvj483n4fsb5js84smwg8331stbs >> Design doc: >> https://docs.google.com/document/d/1NTQhgNbP2dkIMuXUMA5JdwliVQKCp1TU_ux5J_AaPiw/edit?tab=t.0 >> Java impl: https://github.com/apache/iceberg/pull/16160
Re: [VOTE] OpenAPI: Add CatalogObjectIdentifier schema
+1 (non binding) Regards JB On Tue, May 12, 2026 at 10:00 PM Steven Wu wrote: > Hi everyone, > > I propose adding the CatalogObjectIdentifier schema to the REST catalog > OpenAPI spec. > PR: https://github.com/apache/iceberg/pull/16144 > > Summary: > >- CatalogObjectIdentifier is an ordered list of hierarchical levels (a >JSON array of strings) that identifies any catalog object, such as a table, >view, materialized view, namespace, or function. >- Structurally the same as Namespace; the distinct name signals >"any catalog object" rather than specifically a namespace path. >- The kind of object an identifier refers to is determined by context >(the endpoint, or a companion type discriminator defined by that endpoint), >not by the identifier structure itself. > > > Motivation: multiple concurrent efforts need a generic catalog-object > identifier and would otherwise each introduce their own > >- events endpoint (#12584), >- resolve endpoint (#15830), >- functions endpoint (#15180). > > > Adding one shared schema avoids identifier proliferation as new object > types are added to the spec. > > Please review the PR and vote in the next 72 hours. > > [ ] +1 Add CatalogObjectIdentifier to the REST OpenAPI spec > [ ] +0 > [ ] -1 Do not add CatalogObjectIdentifier because... > > Only PMC members have binding votes, but other community members > are encouraged to cast non-binding votes. This vote will pass if there are > 3 binding +1 votes and more binding +1 votes than -1 votes. > > Thanks, > Steven > > Dev thread: > https://lists.apache.org/thread/w6r3cvj483n4fsb5js84smwg8331stbs > Design doc: > https://docs.google.com/document/d/1NTQhgNbP2dkIMuXUMA5JdwliVQKCp1TU_ux5J_AaPiw/edit?tab=t.0 > Java impl: https://github.com/apache/iceberg/pull/16160 >
Re: [VOTE] OpenAPI: Add CatalogObjectIdentifier schema
+1 (non-binding) Le mer. 13 mai 2026 à 08:31, Christian Thiel a écrit : > +1 (non-binding) > Thanks for driving this! > > huaxin gao schrieb am Di. 12. Mai 2026 um 23:43: > >> +1 >> >> On Tue, May 12, 2026 at 2:38 PM Russell Spitzer < >> [email protected]> wrote: >> >>> +1 Binding >>> >>> On Tue, May 12, 2026 at 4:35 PM Yufei Gu wrote: >>> +1(binding) Thanks Steven. Yufei On Tue, May 12, 2026 at 12:59 PM Steven Wu wrote: > Hi everyone, > > I propose adding the CatalogObjectIdentifier schema to the REST > catalog OpenAPI spec. > PR: https://github.com/apache/iceberg/pull/16144 > > Summary: > >- CatalogObjectIdentifier is an ordered list of hierarchical >levels (a JSON array of strings) that identifies any catalog object, > such >as a table, view, materialized view, namespace, or function. >- Structurally the same as Namespace; the distinct name signals >"any catalog object" rather than specifically a namespace path. >- The kind of object an identifier refers to is determined by >context (the endpoint, or a companion type discriminator defined by > that >endpoint), not by the identifier structure itself. > > > Motivation: multiple concurrent efforts need a generic catalog-object > identifier and would otherwise each introduce their own > >- events endpoint (#12584), >- resolve endpoint (#15830), >- functions endpoint (#15180). > > > Adding one shared schema avoids identifier proliferation as new object > types are added to the spec. > > Please review the PR and vote in the next 72 hours. > > [ ] +1 Add CatalogObjectIdentifier to the REST OpenAPI spec > [ ] +0 > [ ] -1 Do not add CatalogObjectIdentifier because... > > Only PMC members have binding votes, but other community members > are encouraged to cast non-binding votes. This vote will pass if there are > 3 binding +1 votes and more binding +1 votes than -1 votes. > > Thanks, > Steven > > Dev thread: > https://lists.apache.org/thread/w6r3cvj483n4fsb5js84smwg8331stbs > Design doc: > https://docs.google.com/document/d/1NTQhgNbP2dkIMuXUMA5JdwliVQKCp1TU_ux5J_AaPiw/edit?tab=t.0 > Java impl: https://github.com/apache/iceberg/pull/16160 >
Re: [VOTE] OpenAPI: Add CatalogObjectIdentifier schema
+1 (non-binding) Thanks for driving this! huaxin gao schrieb am Di. 12. Mai 2026 um 23:43: > +1 > > On Tue, May 12, 2026 at 2:38 PM Russell Spitzer > wrote: > >> +1 Binding >> >> On Tue, May 12, 2026 at 4:35 PM Yufei Gu wrote: >> >>> +1(binding) Thanks Steven. >>> Yufei >>> >>> >>> On Tue, May 12, 2026 at 12:59 PM Steven Wu wrote: >>> Hi everyone, I propose adding the CatalogObjectIdentifier schema to the REST catalog OpenAPI spec. PR: https://github.com/apache/iceberg/pull/16144 Summary: - CatalogObjectIdentifier is an ordered list of hierarchical levels (a JSON array of strings) that identifies any catalog object, such as a table, view, materialized view, namespace, or function. - Structurally the same as Namespace; the distinct name signals "any catalog object" rather than specifically a namespace path. - The kind of object an identifier refers to is determined by context (the endpoint, or a companion type discriminator defined by that endpoint), not by the identifier structure itself. Motivation: multiple concurrent efforts need a generic catalog-object identifier and would otherwise each introduce their own - events endpoint (#12584), - resolve endpoint (#15830), - functions endpoint (#15180). Adding one shared schema avoids identifier proliferation as new object types are added to the spec. Please review the PR and vote in the next 72 hours. [ ] +1 Add CatalogObjectIdentifier to the REST OpenAPI spec [ ] +0 [ ] -1 Do not add CatalogObjectIdentifier because... Only PMC members have binding votes, but other community members are encouraged to cast non-binding votes. This vote will pass if there are 3 binding +1 votes and more binding +1 votes than -1 votes. Thanks, Steven Dev thread: https://lists.apache.org/thread/w6r3cvj483n4fsb5js84smwg8331stbs Design doc: https://docs.google.com/document/d/1NTQhgNbP2dkIMuXUMA5JdwliVQKCp1TU_ux5J_AaPiw/edit?tab=t.0 Java impl: https://github.com/apache/iceberg/pull/16160 >>>
Re: [VOTE] OpenAPI: Add CatalogObjectIdentifier schema
+1 On Tue, May 12, 2026 at 2:38 PM Russell Spitzer wrote: > +1 Binding > > On Tue, May 12, 2026 at 4:35 PM Yufei Gu wrote: > >> +1(binding) Thanks Steven. >> Yufei >> >> >> On Tue, May 12, 2026 at 12:59 PM Steven Wu wrote: >> >>> Hi everyone, >>> >>> I propose adding the CatalogObjectIdentifier schema to the REST catalog >>> OpenAPI spec. >>> PR: https://github.com/apache/iceberg/pull/16144 >>> >>> Summary: >>> >>>- CatalogObjectIdentifier is an ordered list of hierarchical levels >>>(a JSON array of strings) that identifies any catalog object, such as a >>>table, view, materialized view, namespace, or function. >>>- Structurally the same as Namespace; the distinct name signals >>>"any catalog object" rather than specifically a namespace path. >>>- The kind of object an identifier refers to is determined by >>>context (the endpoint, or a companion type discriminator defined by that >>>endpoint), not by the identifier structure itself. >>> >>> >>> Motivation: multiple concurrent efforts need a generic catalog-object >>> identifier and would otherwise each introduce their own >>> >>>- events endpoint (#12584), >>>- resolve endpoint (#15830), >>>- functions endpoint (#15180). >>> >>> >>> Adding one shared schema avoids identifier proliferation as new object >>> types are added to the spec. >>> >>> Please review the PR and vote in the next 72 hours. >>> >>> [ ] +1 Add CatalogObjectIdentifier to the REST OpenAPI spec >>> [ ] +0 >>> [ ] -1 Do not add CatalogObjectIdentifier because... >>> >>> Only PMC members have binding votes, but other community members >>> are encouraged to cast non-binding votes. This vote will pass if there are >>> 3 binding +1 votes and more binding +1 votes than -1 votes. >>> >>> Thanks, >>> Steven >>> >>> Dev thread: >>> https://lists.apache.org/thread/w6r3cvj483n4fsb5js84smwg8331stbs >>> Design doc: >>> https://docs.google.com/document/d/1NTQhgNbP2dkIMuXUMA5JdwliVQKCp1TU_ux5J_AaPiw/edit?tab=t.0 >>> Java impl: https://github.com/apache/iceberg/pull/16160 >>> >>
Re: [VOTE] OpenAPI: Add CatalogObjectIdentifier schema
+1 Binding On Tue, May 12, 2026 at 4:35 PM Yufei Gu wrote: > +1(binding) Thanks Steven. > Yufei > > > On Tue, May 12, 2026 at 12:59 PM Steven Wu wrote: > >> Hi everyone, >> >> I propose adding the CatalogObjectIdentifier schema to the REST catalog >> OpenAPI spec. >> PR: https://github.com/apache/iceberg/pull/16144 >> >> Summary: >> >>- CatalogObjectIdentifier is an ordered list of hierarchical levels >>(a JSON array of strings) that identifies any catalog object, such as a >>table, view, materialized view, namespace, or function. >>- Structurally the same as Namespace; the distinct name signals >>"any catalog object" rather than specifically a namespace path. >>- The kind of object an identifier refers to is determined by context >>(the endpoint, or a companion type discriminator defined by that >> endpoint), >>not by the identifier structure itself. >> >> >> Motivation: multiple concurrent efforts need a generic catalog-object >> identifier and would otherwise each introduce their own >> >>- events endpoint (#12584), >>- resolve endpoint (#15830), >>- functions endpoint (#15180). >> >> >> Adding one shared schema avoids identifier proliferation as new object >> types are added to the spec. >> >> Please review the PR and vote in the next 72 hours. >> >> [ ] +1 Add CatalogObjectIdentifier to the REST OpenAPI spec >> [ ] +0 >> [ ] -1 Do not add CatalogObjectIdentifier because... >> >> Only PMC members have binding votes, but other community members >> are encouraged to cast non-binding votes. This vote will pass if there are >> 3 binding +1 votes and more binding +1 votes than -1 votes. >> >> Thanks, >> Steven >> >> Dev thread: >> https://lists.apache.org/thread/w6r3cvj483n4fsb5js84smwg8331stbs >> Design doc: >> https://docs.google.com/document/d/1NTQhgNbP2dkIMuXUMA5JdwliVQKCp1TU_ux5J_AaPiw/edit?tab=t.0 >> Java impl: https://github.com/apache/iceberg/pull/16160 >> >
Re: [VOTE] OpenAPI: Add CatalogObjectIdentifier schema
+1(binding) Thanks Steven. Yufei On Tue, May 12, 2026 at 12:59 PM Steven Wu wrote: > Hi everyone, > > I propose adding the CatalogObjectIdentifier schema to the REST catalog > OpenAPI spec. > PR: https://github.com/apache/iceberg/pull/16144 > > Summary: > >- CatalogObjectIdentifier is an ordered list of hierarchical levels (a >JSON array of strings) that identifies any catalog object, such as a table, >view, materialized view, namespace, or function. >- Structurally the same as Namespace; the distinct name signals >"any catalog object" rather than specifically a namespace path. >- The kind of object an identifier refers to is determined by context >(the endpoint, or a companion type discriminator defined by that endpoint), >not by the identifier structure itself. > > > Motivation: multiple concurrent efforts need a generic catalog-object > identifier and would otherwise each introduce their own > >- events endpoint (#12584), >- resolve endpoint (#15830), >- functions endpoint (#15180). > > > Adding one shared schema avoids identifier proliferation as new object > types are added to the spec. > > Please review the PR and vote in the next 72 hours. > > [ ] +1 Add CatalogObjectIdentifier to the REST OpenAPI spec > [ ] +0 > [ ] -1 Do not add CatalogObjectIdentifier because... > > Only PMC members have binding votes, but other community members > are encouraged to cast non-binding votes. This vote will pass if there are > 3 binding +1 votes and more binding +1 votes than -1 votes. > > Thanks, > Steven > > Dev thread: > https://lists.apache.org/thread/w6r3cvj483n4fsb5js84smwg8331stbs > Design doc: > https://docs.google.com/document/d/1NTQhgNbP2dkIMuXUMA5JdwliVQKCp1TU_ux5J_AaPiw/edit?tab=t.0 > Java impl: https://github.com/apache/iceberg/pull/16160 >
