This is an automated email from the ASF dual-hosted git repository.
russellspitzer pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iceberg.git
The following commit(s) were added to refs/heads/main by this push:
new 0de62585ce SPEC: Add referenced-by in loadTable API (#13810)
0de62585ce is described below
commit 0de62585ce376667c2d1dde436b2175ae0dad0ca
Author: Prashant Singh <[email protected]>
AuthorDate: Thu Feb 12 10:48:16 2026 -0800
SPEC: Add referenced-by in loadTable API (#13810)
---
open-api/rest-catalog-open-api.yaml | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/open-api/rest-catalog-open-api.yaml
b/open-api/rest-catalog-open-api.yaml
index 99651924a2..fff71128e5 100644
--- a/open-api/rest-catalog-open-api.yaml
+++ b/open-api/rest-catalog-open-api.yaml
@@ -983,6 +983,7 @@ paths:
schema:
type: string
enum: [ all, refs ]
+ - $ref: '#/components/parameters/referenced-by'
responses:
200:
$ref: '#/components/responses/LoadTableResponse'
@@ -1225,6 +1226,7 @@ paths:
schema:
type: string
description: The plan ID that has been used for server-side scan
planning
+ - $ref: '#/components/parameters/referenced-by'
description: Load vended credentials for a table from the catalog.
responses:
200:
@@ -1589,6 +1591,8 @@ paths:
view. The configuration key "token" is used to pass an access token to
be used as a bearer token
for view requests. Otherwise, a token may be passed using a RFC 8693
token type as a configuration
key. For example, "urn:ietf:params:oauth:token-type:jwt=<JWT-token>".
+ parameters:
+ - $ref: '#/components/parameters/referenced-by'
responses:
200:
$ref: '#/components/responses/LoadViewResponse'
@@ -2008,6 +2012,31 @@ components:
schema:
type: string
+ referenced-by:
+ name: referenced-by
+ in: query
+ description:
+ A comma-separated list of fully qualified view names (namespace and
view name) representing the view
+ reference chain when an entity (table or view) is loaded via a view.
The list should be ordered with the outermost view
+ first, followed by any intermediate views it references, down to the
view that directly references the entity.
+ For a simple case where a view directly references the entity, the
list contains a single view identifier.
+ For nested views (a view referencing another view which references the
entity), the list contains multiple
+ view identifiers representing the complete dependency chain.
+
+ The view identifier is a composite string of the format
{namespace}{separator}{viewName}.
+ The namespace-separator (defined in /config) acts as the delimiter.
+ When parsing, the last occurrence of this separator identifies the
boundary between the namespace and the view name.
+ Multipart namespaces must follow the encoding rules of the parent
parameter in the list namespaces endpoint.
+
+ Multiple view identifiers are separated by commas. Servers should
split the parameter value on comma characters
+ to parse individual view identifiers. If view names contain commas,
they must be url-encoded as %2C.
+
+ Example with multiple views (where prod%1Fanalytics is a nested
namespace which has a quarterly_view which references to monthly_view
+ which then references the entity being loaded) -
prod%1Fanalytics%1Fquarterly_view,prod%1Fanalytics%1Fmonthly_view
+ required: false
+ schema:
+ type: string
+
idempotency-key:
name: Idempotency-Key
in: header
