singhpk234 commented on code in PR #13810:
URL: https://github.com/apache/iceberg/pull/13810#discussion_r2747221829
##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -980,6 +980,30 @@ paths:
schema:
type: string
enum: [ all, refs ]
+ - in: query
+ name: referenced-by
+ description:
+ A comma-separated list of fully qualified view names (namespace
and view name) representing the view
+ reference chain when a table 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 table.
+ For a simple case where a view directly references the table, the
list contains a single view identifier.
+ For nested views (a view referencing another view which references
the table), the list contains multiple
+ view identifiers representing the complete dependency chain.
+
+ Each view identifier has the format namespace.viewName where
multipart namespaces follow the same
+ encoding rules as the `parent` parameter in the list namespaces
endpoint (using `namespace-separator`
+ as defined in `/config`).
+
+ The namespace and view name are separated by a dot. When parsing,
the dot separator is located by
+ finding the first dot character after the last namespace separator.
Review Comment:
Thats a nice call out ! i can see how this can be confusing and
unintentionally be an odd restriction.
> the last namespace part can't contain `.`
How about we say first `.` we reading the FQN of the view name when reading
it from backwards, everything on the left is the namespace and right of the dot
is viewName ?
OR
Just simply repurpose the namespace separator and just say everything to the
right of the last namespace separator is view and left is the namespace
I believe based on the email thread the feedback is to use namespace
seperator, just wanted to double confirm, before I push the spec change !
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
