You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@polaris.apache.org by ad...@apache.org on 2026/05/21 15:29:56 UTC

(polaris) branch main updated: Fix various typos across docs, code, and tooling (#4520)

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

adutra pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/polaris.git


The following commit(s) were added to refs/heads/main by this push:
     new 5aa48bedef Fix various typos across docs, code, and tooling (#4520)
5aa48bedef is described below

commit 5aa48bedef316ce95b0bae9927199fe5af9e5659
Author: Rahul Joshi <vi...@gmail.com>
AuthorDate: Thu May 21 11:29:49 2026 -0400

    Fix various typos across docs, code, and tooling (#4520)
    
    Wide grep across .md/.java/.py/.sh/.yaml found these single-word typos:
    
    - site/content/in-dev/unreleased/command-line-interface.md:221
      "establish a AWS trust" -> "establish an AWS trust"
    - site/content/in-dev/unreleased/generic-table.md:59
      "thrown an TableNotFound Exception" -> "thrown a TableNotFound Exception"
    - site/content/in-dev/unreleased/managing-security/external-pdp/opa.md:27
      "currently an preview feature" -> "currently a preview feature"
    - tools/verify-release/verify-release.sh:515
      "the the set" -> "the set"
    - persistence/nosql/persistence/impl/.../CaffeineCacheBackend.java:193
      "Weight of of rejected cache-puts" -> "Weight of rejected cache-puts"
      (this string is a Micrometer metric description visible in ops dashboards)
    - persistence/nosql/persistence/cdi/README.md:37
      "what the the NoSQL" -> "what the NoSQL"
    - helm/polaris/tests/hpa_test.yaml:48
      "(with with autoscaling enabled)" -> "(with autoscaling enabled)"
    
    No logic change; output-only string fixes.
---
 helm/polaris/tests/hpa_test.yaml                                        | 2 +-
 persistence/nosql/persistence/cdi/README.md                             | 2 +-
 .../polaris/persistence/nosql/impl/cache/CaffeineCacheBackend.java      | 2 +-
 site/content/in-dev/unreleased/command-line-interface.md                | 2 +-
 site/content/in-dev/unreleased/generic-table.md                         | 2 +-
 site/content/in-dev/unreleased/managing-security/external-pdp/opa.md    | 2 +-
 tools/verify-release/verify-release.sh                                  | 2 +-
 7 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/helm/polaris/tests/hpa_test.yaml b/helm/polaris/tests/hpa_test.yaml
index 9c1054d6b4..1ca905c78c 100644
--- a/helm/polaris/tests/hpa_test.yaml
+++ b/helm/polaris/tests/hpa_test.yaml
@@ -45,7 +45,7 @@ tests:
           kind: HorizontalPodAutoscaler
           apiVersion: autoscaling/v2
 
-  # metadata.name (with with autoscaling enabled)
+  # metadata.name (with autoscaling enabled)
   - it: should set HPA name
     set:
       autoscaling.enabled: true
diff --git a/persistence/nosql/persistence/cdi/README.md b/persistence/nosql/persistence/cdi/README.md
index 2f353b7fff..e61e5eef35 100644
--- a/persistence/nosql/persistence/cdi/README.md
+++ b/persistence/nosql/persistence/cdi/README.md
@@ -34,7 +34,7 @@ The biggest difference between the Quarkus and Weld variants is the way how data
 `Backend` instances are produced, because the Weld variant targets testing purposes.
 * Weld locates the `Backend` instances using Java's service loader mechanism via 
   `org.apache.polaris.persistence.nosql.api.backend.BackendLoader.findFactoryByName()`, which is
-  also what the the NoSQL persistence JUnit test extension uses.
+  also what the NoSQL persistence JUnit test extension uses.
 * In Quarkus, the `Backend` instances are located using a CDI identifier-based mechanism.
   There are also backend specific builders that leverage Quarkus extensions for the respective
   database backends.
diff --git a/persistence/nosql/persistence/impl/src/main/java/org/apache/polaris/persistence/nosql/impl/cache/CaffeineCacheBackend.java b/persistence/nosql/persistence/impl/src/main/java/org/apache/polaris/persistence/nosql/impl/cache/CaffeineCacheBackend.java
index 56502b056a..a3086f4f3e 100644
--- a/persistence/nosql/persistence/impl/src/main/java/org/apache/polaris/persistence/nosql/impl/cache/CaffeineCacheBackend.java
+++ b/persistence/nosql/persistence/impl/src/main/java/org/apache/polaris/persistence/nosql/impl/cache/CaffeineCacheBackend.java
@@ -190,7 +190,7 @@ class CaffeineCacheBackend implements CacheBackend {
                       .register(reg);
                   var rejectedWeightSummary =
                       DistributionSummary.builder(METER_CACHE_REJECTED_WEIGHT)
-                          .description("Weight of of rejected cache-puts in bytes.")
+                          .description("Weight of rejected cache-puts in bytes.")
                           .tag("cache", CACHE_NAME)
                           .baseUnit(BaseUnits.BYTES)
                           .register(reg);
diff --git a/site/content/in-dev/unreleased/command-line-interface.md b/site/content/in-dev/unreleased/command-line-interface.md
index 0fc265256f..9b0e11a3a0 100644
--- a/site/content/in-dev/unreleased/command-line-interface.md
+++ b/site/content/in-dev/unreleased/command-line-interface.md
@@ -218,7 +218,7 @@ External Catalog Federation: Bearer Token Options:
 External Catalog Federation: AWS SigV4 Options:
   --catalog-role-arn CATALOG_ROLE_ARN                                  The AWS IAM role ARN assumed by Polaris when signing requests
   --catalog-role-session-name CATALOG_ROLE_SESSION_NAME                The role session name to be used by the SigV4 protocol for signing requests
-  --catalog-external-id CATALOG_EXTERNAL_ID                            An optional external ID used to establish a AWS trust relationship
+  --catalog-external-id CATALOG_EXTERNAL_ID                            An optional external ID used to establish an AWS trust relationship
   --catalog-signing-region CATALOG_SIGNING_REGION                      Region to be used by the SigV4 protocol for signing requests
   --catalog-signing-name CATALOG_SIGNING_NAME                          The service name to be used by the SigV4 protocol for signing requests
 ```
diff --git a/site/content/in-dev/unreleased/generic-table.md b/site/content/in-dev/unreleased/generic-table.md
index e1c9672e1b..9ac666b5e9 100644
--- a/site/content/in-dev/unreleased/generic-table.md
+++ b/site/content/in-dev/unreleased/generic-table.md
@@ -56,7 +56,7 @@ shows the comparison between the two APIs:
 |--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
 | Create Table | Create an Iceberg table                                                                                                                                             | Create a generic table                                                                                                        |
 | Load Table   | Load an Iceberg table. If the table to load is a generic table, you need to call the Generic Table loadTable API, otherwise a TableNotFoundException will be thrown | Load a generic table. Similarly, try to load an Iceberg table through Generic Table API will thrown a TableNotFoundException. |
-| Drop Table   | Drop an Iceberg table. Similar as load table, if the table to drop is a Generic table, a tableNotFoundException will be thrown.                                     | Drop a generic table. Drop an Iceberg table through Generic table endpoint will thrown an TableNotFound Exception             |
+| Drop Table   | Drop an Iceberg table. Similar as load table, if the table to drop is a Generic table, a tableNotFoundException will be thrown.                                     | Drop a generic table. Drop an Iceberg table through Generic table endpoint will thrown a TableNotFound Exception              |
 | List Table   | List all Iceberg tables                                                                                                                                             | List all generic tables                                                                                                       |
 
 Note that generic table shares the same namespace with Iceberg tables, the table name has to be unique under the same namespace.
diff --git a/site/content/in-dev/unreleased/managing-security/external-pdp/opa.md b/site/content/in-dev/unreleased/managing-security/external-pdp/opa.md
index b23346eb33..606edba94b 100644
--- a/site/content/in-dev/unreleased/managing-security/external-pdp/opa.md
+++ b/site/content/in-dev/unreleased/managing-security/external-pdp/opa.md
@@ -24,7 +24,7 @@ weight: 100
 ---
 
 {{< alert warning "Preview Feature" >}}
-**OPA integration is currently an preview feature** and may undergo breaking changes in future versions. Use with caution in production environments.
+**OPA integration is currently a preview feature** and may undergo breaking changes in future versions. Use with caution in production environments.
 {{< /alert >}}
 
 This page describes how to integrate Apache Polaris with [Open Policy Agent (OPA)](https://www.openpolicyagent.org/) for external authorization.
diff --git a/tools/verify-release/verify-release.sh b/tools/verify-release/verify-release.sh
index bb1d3ab4a7..b293963a54 100755
--- a/tools/verify-release/verify-release.sh
+++ b/tools/verify-release/verify-release.sh
@@ -512,7 +512,7 @@ mkdir -p "${maven_local_dir}"
 )
 log_part_end
 
-# Check that the the set of locally built Maven artifacts and staged Maven artifacts is the same.
+# Check that the set of locally built Maven artifacts and staged Maven artifacts is the same.
 echo "Listing locally built Maven artifacts..."
 (cd "${maven_local_dir}" ; find . -mindepth 1 -type f "${find_excludes[@]}" -print) \
   | sort \