-
Notifications
You must be signed in to change notification settings - Fork 3.2k
OpenAPI: Add CatalogObjectIdentifier schema #16144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2267,6 +2267,17 @@ components: | |
| type: string | ||
| nullable: false | ||
|
|
||
| CatalogObjectIdentifier: | ||
| description: | ||
| Reference to a catalog object (table, view, or namespace) as an | ||
| ordered list of hierarchical levels. | ||
| The object kind is determined by context (e.g. the endpoint or a | ||
| companion type discriminator), not by the identifier structure alone. | ||
| type: array | ||
| items: | ||
| type: string | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we apply any constraints on the table/view/namespace name? For example, no slash(/) is allowed. Given we didn't specify any constraint on the table identifier, it's not a blocker for this PR. We can work on that as a followup. We can also discuss whether we could avoid any constraints in IRC, and relying on the implementations(catalogs, engines) to cast their options.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We have previously let folks do whatever they want in string fields and left it up to the implementation to decide whether or not that string is invalid. |
||
| example: [ "accounting", "tax", "paid" ] | ||
|
|
||
| PrimitiveType: | ||
| type: string | ||
| example: | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add "for example" to the list, so we don't need to maintain it if we add functions, indexes etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. Reworded to "Reference to a catalog object (for example, table, view, or namespace)" so the list reads as illustrative and doesn't need to be maintained as new kinds (functions, indexes, etc.) are added. Pushed in 9c2ed0a.