Merge branch 'main' into sean/dropwizard-logging

apache · Oct 18, 2024 · 4a75a73 · 4a75a73
2 parents 0142d4f + 101a03a
commit 4a75a73
Show file tree

Hide file tree

Showing 3 changed files with 48 additions and 46 deletions.
diff --git a/site/content/community/meetings/2024/_index.adoc b/site/content/community/meetings/2024/_index.adoc
diff --git a/site/content/community/meetings/_index.adoc b/site/content/community/meetings/_index.adoc
@@ -24,3 +24,49 @@ cascade:
   type: docs
   no_list: false
 ---
+
+== Upcoming Meetings
+
+We have bi-weekly community meeting using Google Meet.
+
+Join the https://groups.google.com/u/1/g/polaris-community-sync[polaris-community-sync Google Group].
+
+== Scheduled Meetings
+
+https://docs.google.com/document/d/1TAAMjCtk4KuWSwfxpCBhhK9vM1k_3n7YE4L28slclXU/[Agenda for upcoming Community Meetings]
+
+[cols="1,3"]
+|===
+| Date | Time
+
+| 2024-10-31 | 9:00 AM PST
+
+17:00 CEST
+| 2024-11-14 | 9:00 AM PST
+
+18:00 CET
+| 2024-11-28 | 9:00 AM PST
+
+18:00 CET
+| 2024-12-12 | 9:00 AM PST
+
+18:00 CET
+| 2024-12-26 | 9:00 AM PST
+
+18:00 CET
+| ... |
+|===
+
+== Past Meetings
+
+[cols="1,3,3"]
+|===
+| Date | Notes | Recording
+
+| 2024-10-17
+| https://docs.google.com/document/d/1TAAMjCtk4KuWSwfxpCBhhK9vM1k_3n7YE4L28slclXU/edit?tab=t.0#heading=h.kf4agp8flxjb[Meeting Notes]
+| (no recording)
+|===
+////
+| {{< youtube id=xyz loading=lazy title="Not a Polaris meeting" >}}
+////
diff --git a/spec/rest-catalog-open-api.yaml b/spec/rest-catalog-open-api.yaml
@@ -990,7 +990,7 @@ paths:
           metadata path being within ALLOWED_LOCATIONS, having an EXTERNAL catalog, etc. The intended use
           case for a VALIDATE notification is to allow a remote catalog to pre-validate the general
           settings of a receiving catalog against an intended new table location before possibly creating
-          a table intended for sending notifcations in the remote catalog at all. For a VALIDATE request,
+          a table intended for sending notifications in the remote catalog at all. For a VALIDATE request,
           the specified metadata-location can either be a prospective full metadata file path, or a
           relevant parent directory of the intended table to validate against ALLOWED_LOCATIONS.
         content:
@@ -4061,7 +4061,7 @@ components:
       value: "accounting%1Ftax"
 
     NamespaceAsPathVariable:
-      summary: A single part namespace, as represented in a path paremeter
+      summary: A single part namespace, as represented in a path parameter
       value: "accounting"
 
     NamespaceAlreadyExistsError: