This is an automated email from the ASF dual-hosted git repository. jmclean pushed a commit to branch catalog in repository https://gitbox.apache.org/repos/asf/gravitino.git
commit 8106944f0869a22bfdb6e60777c31e30a90f89f3 Author: Justin Mclean <[email protected]> AuthorDate: Thu Jul 10 16:52:29 2025 +1000 fix catalog --- docs/manage-tags-in-gravitino.md | 2 +- docs/security/access-control.md | 2 +- docs/trino-connector/trino-connector.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/manage-tags-in-gravitino.md b/docs/manage-tags-in-gravitino.md index 04e5b79ec8..16a6c71322 100644 --- a/docs/manage-tags-in-gravitino.md +++ b/docs/manage-tags-in-gravitino.md @@ -24,7 +24,7 @@ the future versions. :::info 1. Metadata objects are objects that are managed in Gravitino, such as `CATALOG`, `SCHEMA`, `TABLE`, `COLUMN`, `FILESET`, `TOPIC`, `COLUMN`, `MODEL`, etc. A metadata object is combined by a `type` and a - comma-separated `name`. For example, a `CATAGLOG` object has a name "catalog1" with type + comma-separated `name`. For example, a `CATALOG` object has a name "catalog1" with type "CATALOG", a `SCHEMA` object has a name "catalog1.schema1" with type "SCHEMA", a `TABLE` object has a name "catalog1.schema1.table1" with type "TABLE", a `COLUMN` object has a name "catalog1.schema1.table1.column1" with type "COLUMN". diff --git a/docs/security/access-control.md b/docs/security/access-control.md index 773ae80200..6948c1803a 100644 --- a/docs/security/access-control.md +++ b/docs/security/access-control.md @@ -114,7 +114,7 @@ This process allows all users belonging to that user group to have the access co Metadata objects are managed in Gravitino, such as `CATALOG`, `SCHEMA`, `TABLE`, `COLUMN`, `FILESET`, `TOPIC`, `COLUMN`, `ROLE`, `METALAKE`. A metadata object is combined by a `type` and a -comma-separated `name`. For example, a `CATAGLOG` object has a name "catalog1" with type +comma-separated `name`. For example, a `CATALOG` object has a name "catalog1" with type "CATALOG", a `SCHEMA` object has a name "catalog1.schema1" with type "SCHEMA", a `TABLE` object has a name "catalog1.schema1.table1" with type "TABLE". A `METALAKE` object has a name "metalake1". diff --git a/docs/trino-connector/trino-connector.md b/docs/trino-connector/trino-connector.md index 37cb67b1d0..6f22fe7b4f 100644 --- a/docs/trino-connector/trino-connector.md +++ b/docs/trino-connector/trino-connector.md @@ -9,7 +9,7 @@ Trino can manage and access data using the Trino connector provided by `Apache G After configuring the Gravitino Trino connector in Trino, Trino can automatically load catalog metadata from Gravitino, allowing users to directly access these catalogs in Trino. Once integrated with Gravitino, Trino can operate on all Gravitino data without requiring additional configuration. The Gravitino Trino connector uses the [Trino dynamic catalog managed mechanism](https://trino.io/docs/current/admin/properties-catalog.html) to load catalogs. -When the Gravitino Trino connector retrieves catalogs from the Gravitino server, it generates a `CREATE CATAGLOG` statement and executes +When the Gravitino Trino connector retrieves catalogs from the Gravitino server, it generates a `CREATE CATALOG` statement and executes the statement on the current Trino server to register the catalogs with Trino :::note
