BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20250224T090000
DTEND;TZID=America/Los_Angeles:20250224T100000
DTSTAMP:20250222T013242Z
ORGANIZER;CN=yun zou:mailto:yunzou.colost...@gmail.com
UID:4n4nh6rcecni60d9umcrdan...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=yun zou;X-NUM-GUESTS=0:mailto:yunzou.colost...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@polaris.apache.org;X-NUM-GUESTS=0:mailto:dev@polaris.apache.org
X-GOOGLE-CONFERENCE:https://meet.google.com/izz-zuix-fwc
X-MICROSOFT-CDO-OWNERAPPTID:-2020777751
CREATED:20250222T004448Z
DESCRIPTION:<a href="https://polaris.apache.org/"; target="_blank"><u>Apache
  Polaris </u></a>currently only functions as a catalog for <a href="https:/
 /iceberg.apache.org/" target="_blank"><u>Apache Iceberg</u></a> tables thro
 ugh the Iceberg REST Catalog API. However\, many users or engines (i.e.<a h
 ref="https://spark.apache.org/"; target="_blank"><u> Apache Spark</u></a>\, 
 <a href="https://trino.io/"; target="_blank"><u>Trino</u></a>\, <a href="htt
 ps://docs.snowflake.com/en/user-guide/intro-key-concepts" target="_blank"><
 u>Snowflake</u></a> etc) also work with other table formats like <a href="h
 ttps://github.com/delta-io/delta" target="_blank"><u>Delta</u></a>. In orde
 r for Polaris to provide better interoperability across different engines\,
  we should provide the capability for Polaris to manage non-Iceberg tables\
 , which we call <b>Generic Table</b> in Polaris. <br><br>In this proposal\,
  we propose a way <span>to provide capabilities in Polaris to manage Generi
 c tables\, as well as a Spark Catalog plugin for Spark to work with Polaris
 .</span><br><span><br></span><br><span>Here is a link to the proposal </spa
 n><a href="https://docs.google.com/document/d/1_R9jBIwoH3CV9G7gSoRJPQVEcOsR
 Op4IEiGoeYeQE8A/edit?tab=t.0" target="_blank">https://docs.google.com/docum
 ent/d/1_R9jBIwoH3CV9G7gSoRJPQVEcOsROp4IEiGoeYeQE8A/edit?tab=t.0</a><br><br>
 Looking forward to see you in the review meeting.<br><br>Best Regards\,<br>
 Yun\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~::~:~::-\nJoin with Google Meet: https://meet.google.com/izz-zui
 x-fwc\n\nLearn more about Meet at: https://support.google.com/a/users/answe
 r/9282720\n\nPlease do not edit this section.\n-::~:~::~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20250222T013241Z
LOCATION:
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:Review: Generic Table Support in Apache Polaris
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:EMAIL
DESCRIPTION:This is an event reminder
SUMMARY:Alarm notification
ATTENDEE:mailto:dev@polaris.apache.org
TRIGGER:-P0DT0H10M0S
END:VALARM
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H30M0S
END:VALARM
END:VEVENT
END:VCALENDAR

Attachment: invite.ics
Description: application/ics



Reply via email to