This is an automated email from the ASF dual-hosted git repository.

yuqi1129 pushed a commit to branch branch-1.3
in repository https://gitbox.apache.org/repos/asf/gravitino.git


The following commit(s) were added to refs/heads/branch-1.3 by this push:
     new 245462adf2 [Cherry-pick to branch-1.3] [#13634] Fix incorrect 
privilege scopes, Kafka property name and CLI link in docs (#13635) (#13641)
245462adf2 is described below

commit 245462adf24a3d6c18f4d4300051052ed2b36746
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu Oct 1 09:50:48 2026 +0800

    [Cherry-pick to branch-1.3] [#13634] Fix incorrect privilege scopes, Kafka 
property name and CLI link in docs (#13635) (#13641)
    
    **Cherry-pick Information:**
    - Original commit: 6f5c640f0a846e7de15c7f6b7062cfeca3638314
    - Target branch: `branch-1.3`
    - Status: ✅ Clean cherry-pick (no conflicts)
    
    Co-authored-by: Bharath Krishna <[email protected]>
---
 .../apache/gravitino/catalog/kafka/KafkaTopicPropertiesMetadata.java  | 2 +-
 docs/filesets.md                                                      | 2 +-
 docs/functions.md                                                     | 4 ++--
 docs/kafka-catalog.md                                                 | 2 +-
 docs/table-maintenance-service/optimizer-extension-guide.md           | 2 +-
 docs/topics.md                                                        | 4 ++--
 6 files changed, 8 insertions(+), 8 deletions(-)

diff --git 
a/catalogs/catalog-kafka/src/main/java/org/apache/gravitino/catalog/kafka/KafkaTopicPropertiesMetadata.java
 
b/catalogs/catalog-kafka/src/main/java/org/apache/gravitino/catalog/kafka/KafkaTopicPropertiesMetadata.java
index 773b670037..f74df52a7f 100644
--- 
a/catalogs/catalog-kafka/src/main/java/org/apache/gravitino/catalog/kafka/KafkaTopicPropertiesMetadata.java
+++ 
b/catalogs/catalog-kafka/src/main/java/org/apache/gravitino/catalog/kafka/KafkaTopicPropertiesMetadata.java
@@ -37,7 +37,7 @@ public class KafkaTopicPropertiesMetadata extends 
BasePropertiesMetadata {
             PropertyEntry.integerOptionalPropertyEntry(
                 PARTITION_COUNT,
                 "The number of partitions for the topic, if not specified, "
-                    + "will use the num.partition property in the broker",
+                    + "will use the num.partitions property in the broker",
                 false /* immutable */,
                 null /* default value */,
                 false /* hidden */),
diff --git a/docs/filesets.md b/docs/filesets.md
index 06b52929d7..174a806951 100644
--- a/docs/filesets.md
+++ b/docs/filesets.md
@@ -93,7 +93,7 @@ today. Attaching a tag to a fileset goes through the API.
 
 | Privilege        | Grantable on                          | What it allows    
          |
 
|------------------|---------------------------------------|-----------------------------|
-| `CREATE_FILESET` | Metalake, catalog, schema, or fileset | Creating filesets 
          |
+| `CREATE_FILESET` | Metalake, catalog, or schema          | Creating filesets 
          |
 | `READ_FILESET`   | Metalake, catalog, schema, or fileset | Reading a 
fileset's files   |
 | `WRITE_FILESET`  | Metalake, catalog, schema, or fileset | Writing a 
fileset's files   |
 
diff --git a/docs/functions.md b/docs/functions.md
index e3c8fe383a..483563fc6a 100644
--- a/docs/functions.md
+++ b/docs/functions.md
@@ -55,7 +55,7 @@ definitions is the same name accepting different arguments, 
the way `round(x)` a
 are one function in most engines.
 
 An implementation is how a definition is expressed for a given engine. Each 
declares a language and
-a runtime, so one definition can carry a SQL version for Trino and a Python 
version for Spark, and
+a runtime, so one definition can carry a SQL version for Trino and a Java 
version for Spark, and
 each engine uses the one it can execute.
 
 | Language | Carries                                          |
@@ -79,7 +79,7 @@ all go through the API, as does attaching a tag, which the 
function page does no
 
 | Privilege           | Grantable on                           | What it 
allows                    |
 
|---------------------|----------------------------------------|-----------------------------------|
-| `REGISTER_FUNCTION` | Metalake, catalog, schema, or function | Registering 
functions             |
+| `REGISTER_FUNCTION` | Metalake, catalog, or schema           | Registering 
functions             |
 | `EXECUTE_FUNCTION`  | Metalake, catalog, schema, or function | Calling a 
function from an engine |
 | `MODIFY_FUNCTION`   | Metalake, catalog, schema, or function | Altering a 
registered function    |
 
diff --git a/docs/kafka-catalog.md b/docs/kafka-catalog.md
index 6cabf2abeb..3f561eb28a 100644
--- a/docs/kafka-catalog.md
+++ b/docs/kafka-catalog.md
@@ -52,7 +52,7 @@ Refer to [Schema 
operation](./manage-messaging-metadata-using-gravitino.md#schem
 
 | Property name        | Description                              | Default 
value                                                                       | 
Required |
 
|----------------------|------------------------------------------|-------------------------------------------------------------------------------------|----------|
-| `partition-count`    | The number of partitions for the topic.  | if not 
specified, will use the `num.partition` property in the broker.              | 
No       |
+| `partition-count`    | The number of partitions for the topic.  | if not 
specified, will use the `num.partitions` property in the broker.              | 
No       |
 | `replication-factor` | The number of replications for the topic | if not 
specified, will use the `default.replication.factor` property in the broker. | 
No       |
 
 Pass other topic configurations to the topic properties. Refer to [Topic 
Configs](https://kafka.apache.org/34/documentation.html#topicconfigs) for more 
details.
diff --git a/docs/table-maintenance-service/optimizer-extension-guide.md 
b/docs/table-maintenance-service/optimizer-extension-guide.md
index 9d33021cb1..8193636414 100644
--- a/docs/table-maintenance-service/optimizer-extension-guide.md
+++ b/docs/table-maintenance-service/optimizer-extension-guide.md
@@ -127,5 +127,5 @@ If you also extend Gravitino server job execution, see 
[Manage jobs in Gravitino
 
 - [Table Maintenance Service](./optimizer.md)
 - [Configuration](./optimizer-configuration.md)
-- [CLI Reference](./optimizer-configuration.md)
+- [CLI Reference](./optimizer-cli-reference.md)
 - [Troubleshooting](./optimizer-troubleshooting.md)
diff --git a/docs/topics.md b/docs/topics.md
index 53dfa9f926..c376a997a2 100644
--- a/docs/topics.md
+++ b/docs/topics.md
@@ -52,7 +52,7 @@ A topic name is unique within its schema, and matches the 
topic name in the clus
 
 Two properties are settable at creation. `partition-count` sets the number of 
partitions and can be
 changed afterward. `replication-factor` sets the replication and is immutable 
once the topic exists.
-Leaving either unset takes the broker's own default, from `num.partition` and
+Leaving either unset takes the broker's own default, from `num.partitions` and
 `default.replication.factor` respectively.
 
 ### What Gravitino Stores and What It Does Not
@@ -76,7 +76,7 @@ the UI today. Attaching a tag to a topic goes through the API.
 
 | Privilege       | Grantable on                        | What it allows       
 |
 
|-----------------|-------------------------------------|-----------------------|
-| `CREATE_TOPIC`  | Metalake, catalog, schema, or topic | Creating topics      
 |
+| `CREATE_TOPIC`  | Metalake, catalog, or schema        | Creating topics      
 |
 | `PRODUCE_TOPIC` | Metalake, catalog, schema, or topic | Writing to a topic   
 |
 | `CONSUME_TOPIC` | Metalake, catalog, schema, or topic | Reading from a topic 
 |
 

Reply via email to