Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/command-line-interface.md
Original file line number Diff line number Diff line change
Expand Up @@ -797,7 +797,7 @@ polaris namespaces list --catalog my_catalog --parent a.b

### Privileges

The `privileges` command is used to grant various privileges to a catalog role, or to revoke those privileges. Privileges can be on the level of a catalog, a namespace, a table, or a view. For more information on privileges, please refer to the [docs](./entities.md#privilege).
The `privileges` command is used to grant various privileges to a catalog role, or to revoke those privileges. Privileges can be on the level of a catalog, a namespace, a table, or a view. For more information on privileges, please refer to the [docs](https://polaris.io/#tag/Polaris-Catalog-Entities/Privilege).
Copy link
Contributor

@eric-maynard eric-maynard Aug 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want the docs to point to internet URLs like this? That makes them not work offline. One alternative is to use local HTML docs like Apache Spark does (e.g.)


Note that when using the `privileges` command, the user specifies the relevant catalog and catalog role before selecting a subcommand.

Expand Down
22 changes: 11 additions & 11 deletions docs/entities.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,46 +20,46 @@ This page documents various entities that can be managed in Polaris.

A catalog is a top-level entity in Polaris that may contain other entities like [namespaces](#namespace) and [tables](#table). These map directly to [Apache Iceberg catalogs](https://iceberg.apache.org/concepts/catalog/).

For information on managing catalogs with the REST API or for more information on what data can be associated with a catalog, see [the API docs](../regtests/client/python/docs/CreateCatalogRequest.md).
For information on managing catalogs with the REST API or for more information on what data can be associated with a catalog, see [the API docs](https://github.com/polaris-catalog/polaris/blob/main/regtests/client/python/docs/CreateCatalogRequest.md).

### Storage Type

All catalogs in Polaris are associated with a _storage type_. Valid Storage Types are `S3`, `Azure`, and `GCS`. The `FILE` type is also additionally available for testing. Each of these types relates to a different storage provider where data within the catalog may reside. Depending on the storage type, various other configurations may be set for a catalog including credentials to be used when accessing data inside the catalog.

For details on how to use Storage Types in the REST API, see [the API docs](../regtests/client/python/docs/StorageConfigInfo.md).
For details on how to use Storage Types in the REST API, see [the API docs](https://github.com/polaris-catalog/polaris/blob/main/regtests/client/python/docs/StorageConfigInfo.md).

## Namespace

A namespace is a logical entity that resides within a [catalog](#catalog) and can contain other entities such as [tables](#table) or [views](#view). Some other systems may refer to namespaces as _schemas_ or _databases_.

In Polaris, namespaces can be nested. For example, `a.b.c.d.e.f.g` is a valid namespace. `b` is said to reside within `a`, and so on.

For information on managing namespaces with the REST API or for more information on what data can be associated with a namespace, see [the API docs](../regtests/client/python/docs/CreateNamespaceRequest.md).
For information on managing namespaces with the REST API or for more information on what data can be associated with a namespace, see [the API docs](https://github.com/polaris-catalog/polaris/blob/main/regtests/client/python/docs/CreateNamespaceRequest.md).


## Table

Polaris tables are entities that map to [Apache Iceberg tables](https://iceberg.apache.org/docs/nightly/configuration/).

For information on managing tables with the REST API or for more information on what data can be associated with a table, see [the API docs](../regtests/client/python/docs/CreateTableRequest.md).
For information on managing tables with the REST API or for more information on what data can be associated with a table, see [the API docs](https://github.com/polaris-catalog/polaris/blob/main/regtests/client/python/docs/CreateTableRequest.md).

## View

Polaris views are entities that map to [Apache Iceberg views](https://iceberg.apache.org/view-spec/).

For information on managing views with the REST API or for more information on what data can be associated with a view, see [the API docs](../regtests/client/python/docs/CreateViewRequest.md).
For information on managing views with the REST API or for more information on what data can be associated with a view, see [the API docs](https://github.com/polaris-catalog/polaris/blob/main/regtests/client/python/docs/CreateViewRequest.md).

## Principal

Polaris principals are unique identities that can be used to represent users or services. Each principal may have one or more [principal roles](#principal-role) assigned to it for the purpose of accessing catalogs and the entities within them.

For information on managing principals with the REST API or for more information on what data can be associated with a principal, see [the API docs](../regtests/client/python/docs/CreatePrincipalRequest.md).
For information on managing principals with the REST API or for more information on what data can be associated with a principal, see [the API docs](https://github.com/polaris-catalog/polaris/blob/main/regtests/client/python/docs/CreatePrincipalRequest.md).

## Principal Role

Polaris principal roles are labels that may be granted to [principals](#principal). Each principal may have one or more principal roles, and the same principal role may be granted to multiple principals. Principal roles may be assigned based on the persona or responsibilities of a given principal, or on how that principal will need to access different entities within Polaris.

For information on managing principal roles with the REST API or for more information on what data can be associated with a principal role, see [the API docs](../regtests/client/python/docs/CreatePrincipalRoleRequest.md).
For information on managing principal roles with the REST API or for more information on what data can be associated with a principal role, see [the API docs](https://github.com/polaris-catalog/polaris/blob/main/regtests/client/python/docs/CreatePrincipalRoleRequest.md).


## Catalog Role
Expand All @@ -75,7 +75,7 @@ Polaris privileges are granted to [catalog roles](#catalog-role) in order to gra
A privilege can be scoped to any entity inside a catalog, including the catalog itself.

For a list of supported privileges for each privilege class, see the API docs:
* [Table Privileges](../regtests/client/python/docs/TablePrivilege.md)
* [View Privileges](../regtests/client/python/docs/ViewPrivilege.md)
* [Namespace Privileges](../regtests/client/python/docs/NamespacePrivilege.md)
* [Catalog Privileges](../regtests/client/python/docs/CatalogPrivilege.md)
* [Table Privileges](https://github.com/polaris-catalog/polaris/blob/main/regtests/client/python/docs/TablePrivilege.md)
* [View Privileges](https://github.com/polaris-catalog/polaris/blob/main/regtests/client/python/docs/ViewPrivilege.md)
* [Namespace Privileges](https://github.com/polaris-catalog/polaris/blob/main/regtests/client/python/docs/NamespacePrivilege.md)
* [Catalog Privileges](https://github.com/polaris-catalog/polaris/blob/main/regtests/client/python/docs/CatalogPrivilege.md)
Loading