dev  

Messages by Thread

• [RESULT][VOTE] Release Apache Polaris 1.6.0 (rc0) EJ Wang
  • Re: [RESULT][VOTE] Release Apache Polaris 1.6.0 (rc0) Jean-Baptiste Onofré
• [DISCUSS] Feature-specific SQL DDL files Dmitri Bourlatchkov
  • Re: [DISCUSS] Feature-specific SQL DDL files Yufei Gu
• [DISCUSS] Single SQL DDL script Dmitri Bourlatchkov
• Please add me to the Polaris Slack, thanks! <EOM> Tarun Jangid
  • Re: Please add me to the Polaris Slack, thanks! <EOM> Yufei Gu
• JB's back :) Jean-Baptiste Onofré
  • Re: JB's back :) Kevin Liu
  • Re: JB's back :) Danica Fine
  • Re: JB's back :) Keith Chapman
• [DISCUSS] Jackson 3 readiness for Polaris and Quarkus 4 Robert Stupp
  • Re: [DISCUSS] Jackson 3 readiness for Polaris and Quarkus 4 Alexandre Dutra
  • Re: [DISCUSS] Jackson 3 readiness for Polaris and Quarkus 4 Romain Manni-Bucau
  • Re: [DISCUSS] Jackson 3 readiness for Polaris and Quarkus 4 Robert Stupp
  • Re: [DISCUSS] Jackson 3 readiness for Polaris and Quarkus 4 Romain Manni-Bucau
  • Re: [DISCUSS] Jackson 3 readiness for Polaris and Quarkus 4 Jean-Baptiste Onofré
  • Re: [DISCUSS] Jackson 3 readiness for Polaris and Quarkus 4 Yufei Gu
  • Re: [DISCUSS] Jackson 3 readiness for Polaris and Quarkus 4 Robert Stupp
  • Re: [DISCUSS] Jackson 3 readiness for Polaris and Quarkus 4 Yufei Gu
  • Re: [DISCUSS] Jackson 3 readiness for Polaris and Quarkus 4 Alexandre Dutra
  • Re: [DISCUSS] Jackson 3 readiness for Polaris and Quarkus 4 Yufei Gu
• [DISCUSS] Modular design for new features Dmitri Bourlatchkov
  • Re: [DISCUSS] Modular design for new features Russell Spitzer
  • Re: [DISCUSS] Modular design for new features Dmitri Bourlatchkov
  • Re: [DISCUSS] Modular design for new features Anand Kumar Sankaran via dev
  • Re: [DISCUSS] Modular design for new features Yufei Gu
  • Re: [DISCUSS] Modular design for new features Robert Stupp
  • Re: [DISCUSS] Modular design for new features Yufei Gu
  • Re: [DISCUSS] Modular design for new features Robert Stupp
• [DISCUSS] NoSQL backend missing entity cache - gap worth addressing? vignesh a
  • Re: [DISCUSS] NoSQL backend missing entity cache - gap worth addressing? Dmitri Bourlatchkov
  • Re: [DISCUSS] NoSQL backend missing entity cache - gap worth addressing? vignesh a
  • Re: [DISCUSS] NoSQL backend missing entity cache - gap worth addressing? Dmitri Bourlatchkov
• [DISCUSS] OpenTelemetry event listener Dmitri Bourlatchkov
  • Re: [DISCUSS] OpenTelemetry event listener Adnan Hemani via dev
• [VOTE] Release Apache Polaris 1.6.0 (rc0) EJ Wang
  • Re: [VOTE] Release Apache Polaris 1.6.0 (rc0) EJ Wang
  • Re: [VOTE] Release Apache Polaris 1.6.0 (rc0) Adnan Hemani via dev
  • Re: [VOTE] Release Apache Polaris 1.6.0 (rc0) Adnan Hemani via dev
  • Re: [VOTE] Release Apache Polaris 1.6.0 (rc0) Alexandre Dutra
  • Re: [VOTE] Release Apache Polaris 1.6.0 (rc0) Jean-Baptiste Onofré
  • Re: [VOTE] Release Apache Polaris 1.6.0 (rc0) Adnan Hemani via dev
  • Re: [VOTE] Release Apache Polaris 1.6.0 (rc0) EJ Wang
• CI is broken on setup-gradle Yong Zheng
  • Re: CI is broken on setup-gradle Yufei Gu
  • Re: CI is broken on setup-gradle Dmitri Bourlatchkov
  • Re: CI is broken on setup-gradle Robert Stupp
  • Re: CI is broken on setup-gradle Yufei Gu
• [DISCUSS] Nullability in PolarisResolutionManifest -- broader cleanup? imavignesh27
  • Re: [DISCUSS] Nullability in PolarisResolutionManifest -- broader cleanup? Dmitri Bourlatchkov
  • Re: [DISCUSS] Nullability in PolarisResolutionManifest -- broader cleanup? vignesh a
• [DISCUSS] Remove TestEnvironmentExtension Alexandre Dutra
  • Re: [DISCUSS] Remove TestEnvironmentExtension Dmitri Bourlatchkov
• [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Yufei Gu
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Adam Christian
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Adnan Hemani via dev
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Adnan Hemani via dev
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Adnan Hemani via dev
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Russell Spitzer
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Adnan Hemani via dev
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Adnan Hemani via dev
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Adnan Hemani via dev
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Yufei Gu
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Robert Stupp
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Adnan Hemani via dev
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses yun zou
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Robert Stupp
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Alexandre Dutra
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Alexandre Dutra
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Yufei Gu
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
  • Re: [DISCUSS] Non-IRC endpoints in IRC config responses Dmitri Bourlatchkov
• [DISCUSS] Multiple datasources with runtime activation Alexandre Dutra
  • Re: [DISCUSS] Multiple datasources with runtime activation Alexandre Dutra
  • Re: [DISCUSS] Multiple datasources with runtime activation Romain Manni-Bucau
  • Re: [DISCUSS] Multiple datasources with runtime activation Alexandre Dutra
  • Re: [DISCUSS] Multiple datasources with runtime activation Romain Manni-Bucau
  • Re: [DISCUSS] Multiple datasources with runtime activation Dmitri Bourlatchkov
  • Re: [DISCUSS] Multiple datasources with runtime activation Romain Manni-Bucau
  • Re: [DISCUSS] Multiple datasources with runtime activation Yufei Gu
  • Re: [DISCUSS] Multiple datasources with runtime activation Dmitri Bourlatchkov
  • Re: [DISCUSS] Multiple datasources with runtime activation Alexandre Dutra
  • Re: [DISCUSS] Multiple datasources with runtime activation Dmitri Bourlatchkov
  • Re: [DISCUSS] Multiple datasources with runtime activation Romain Manni-Bucau
  • Re: [DISCUSS] Multiple datasources with runtime activation Alexandre Dutra
  • Re: [DISCUSS] Multiple datasources with runtime activation Romain Manni-Bucau
  • Re: [DISCUSS] Multiple datasources with runtime activation Yufei Gu
  • Re: [DISCUSS] Multiple datasources with runtime activation Alexandre Dutra
  • Re: [DISCUSS] Multiple datasources with runtime activation Yufei Gu
  • Re: [DISCUSS] Multiple datasources with runtime activation Alexandre Dutra
  • Re: [DISCUSS] Multiple datasources with runtime activation Dmitri Bourlatchkov
• [DISCUSS] Behaviour of PURGE_VIEW_METADATA_ON_DROP Ayush Saxena
  • Re: [DISCUSS] Behaviour of PURGE_VIEW_METADATA_ON_DROP Dmitri Bourlatchkov
• [PROPOSAL] Scan Planning with Optional Caching Layers Tornike Gurgenidze
  • Re: [PROPOSAL] Scan Planning with Optional Caching Layers Yufei Gu
  • Re: [PROPOSAL] Scan Planning with Optional Caching Layers Adnan Hemani via dev
  • Re: [PROPOSAL] Scan Planning with Optional Caching Layers Tornike Gurgenidze
  • Re: [PROPOSAL] Scan Planning with Optional Caching Layers Dmitri Bourlatchkov
  • Re: [PROPOSAL] Scan Planning with Optional Caching Layers Yufei Gu
  • Re: [PROPOSAL] Scan Planning with Optional Caching Layers Prashant Singh
• [Discuss] Handler-level idempotency for createTable (#4659) huaxin gao
  • Re: [Discuss] Handler-level idempotency for createTable (#4659) Dmitri Bourlatchkov
  • Re: [Discuss] Handler-level idempotency for createTable (#4659) Dmitri Bourlatchkov
• [DISCUSS] Removing @Valid annotations from some generated API object builder methods Dmitri Bourlatchkov
• [DISCUSS] Removing PolarisMetricsManager from PolarisMetaStoreManager Dmitri Bourlatchkov
  • Re: [DISCUSS] Removing PolarisMetricsManager from PolarisMetaStoreManager Yufei Gu
• [D] Fine grain Branch/Tag creation control [polaris] via GitHub
  • Re: [D] Fine grain Branch/Tag creation control [polaris] via GitHub
  • Re: [D] Fine grain Branch/Tag creation control [polaris] via GitHub
  • Re: [D] Fine grain Branch/Tag creation control [polaris] via GitHub
• [DISCUSS] Why Polaris needs the server-test-runner Gradle plugin Robert Stupp
  • Re: [DISCUSS] Why Polaris needs the server-test-runner Gradle plugin Alexandre Dutra
• [D] Feasibility of 1 Realm per Tenant at 10,000 Tenants Scale? [polaris] via GitHub
  • Re: [D] Feasibility of 1 Realm per Tenant at 10,000 Tenants Scale? [polaris] via GitHub
  • Re: [D] Feasibility of 1 Realm per Tenant at 10,000 Tenants Scale? [polaris] via GitHub
  • Re: [D] Feasibility of 1 Realm per Tenant at 10,000 Tenants Scale? [polaris] via GitHub
  • Re: [D] Feasibility of 1 Realm per Tenant at 10,000 Tenants Scale? [polaris] via GitHub
  • Re: [D] Feasibility of 1 Realm per Tenant at 10,000 Tenants Scale? [polaris] via GitHub
  • Re: [D] Feasibility of 1 Realm per Tenant at 10,000 Tenants Scale? [polaris] via GitHub
  • Re: [D] Feasibility of 1 Realm per Tenant at 10,000 Tenants Scale? [polaris] via GitHub
  • Re: [D] Feasibility of 1 Realm per Tenant at 10,000 Tenants Scale? [polaris] via GitHub
• Forwarding user-defined principal properties in PolarisPrincipal : PR #4405 Prithvi S
  • Re: Forwarding user-defined principal properties in PolarisPrincipal : PR #4405 Alexandre Dutra
• Improving PolarisAuthorizer 403 messages : PR #4406 Prithvi S
  • Re: Improving PolarisAuthorizer 403 messages : PR #4406 Dmitri Bourlatchkov
  • Re: Improving PolarisAuthorizer 403 messages : PR #4406 Robert Stupp
• [DISCUSS] Deprecate TreeMapMetaStore and friends for removal Alexandre Dutra
  • Re: [DISCUSS] Deprecate TreeMapMetaStore and friends for removal Adnan Hemani via dev
  • Re: [DISCUSS] Deprecate TreeMapMetaStore and friends for removal Jean-Baptiste Onofré
  • Re: [DISCUSS] Deprecate TreeMapMetaStore and friends for removal Dmitri Bourlatchkov
  • Re: [DISCUSS] Deprecate TreeMapMetaStore and friends for removal Alexandre Dutra
  • Re: [DISCUSS] Deprecate TreeMapMetaStore and friends for removal Russell Spitzer
  • Re: [DISCUSS] Deprecate TreeMapMetaStore and friends for removal Alexandre Dutra
• GCP counterpart to AWS STS session tags Anand Kumar Sankaran via dev
  • Re: GCP counterpart to AWS STS session tags Yufei Gu
  • Re: GCP counterpart to AWS STS session tags Adnan Hemani via dev
  • Re: GCP counterpart to AWS STS session tags Jean-Baptiste Onofré
  • Re: GCP counterpart to AWS STS session tags Dmitri Bourlatchkov
  • Re: GCP counterpart to AWS STS session tags Sung Yun
  • Re: GCP counterpart to AWS STS session tags Dmitri Bourlatchkov
  • Re: GCP counterpart to AWS STS session tags Anand Kumar Sankaran via dev
  • Re: GCP counterpart to AWS STS session tags Sung Yun
  • Re: GCP counterpart to AWS STS session tags Adnan Hemani via dev
• [DISCUSS] Fixing the Principal Role validation pattern (REST spec change) Dmitri Bourlatchkov
• [DISCUSS] Semantic JSON comparison in PolarisBaseEntity Dmitri Bourlatchkov
  • Re: [DISCUSS] Semantic JSON comparison in PolarisBaseEntity Venkateshwaran Shanmugham
• [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Yufei Gu
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Alexandre Dutra
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Anand Kumar Sankaran via dev
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Anand Kumar Sankaran via dev
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Dmitri Bourlatchkov
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Yufei Gu
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Alexandre Dutra
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event EJ Wang
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Yong Zheng
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Alexandre Dutra
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Romain Manni-Bucau
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Alexandre Dutra
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Romain Manni-Bucau
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Alexandre Dutra
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Yufei Gu
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Alexandre Dutra
  • Re: [DISCUSS] Facilitate the forwarding use cases of Iceberg Scan and Commit Metrics via Event Yufei Gu
• [DISCUSS] Making unique table locations the default Yufei Gu
  • Re: [DISCUSS] Making unique table locations the default Russell Spitzer
  • Re: [DISCUSS] Making unique table locations the default Dmitri Bourlatchkov
  • Re: [DISCUSS] Making unique table locations the default Yufei Gu
  • Re: [DISCUSS] Making unique table locations the default Dmitri Bourlatchkov
  • Re: [DISCUSS] Making unique table locations the default Yufei Gu
• [DISCUSS] Event delivery: ordering and concurrency guarantees Alexandre Dutra
  • Re: [DISCUSS] Event delivery: ordering and concurrency guarantees Nándor Kollár
  • Re: [DISCUSS] Event delivery: ordering and concurrency guarantees Alexandre Dutra
  • Re: [DISCUSS] Event delivery: ordering and concurrency guarantees Yufei Gu
  • Re: [DISCUSS] Event delivery: ordering and concurrency guarantees Dmitri Bourlatchkov
• [DISCUSS] Status code for table/view rename conflicts Nándor Kollár
  • Re: [DISCUSS] Status code for table/view rename conflicts Dmitri Bourlatchkov
  • Re: [DISCUSS] Status code for table/view rename conflicts Dmitri Bourlatchkov
  • Re: [DISCUSS] Status code for table/view rename conflicts Nándor Kollár
  • Re: [DISCUSS] Status code for table/view rename conflicts Alexandre Dutra
  • Re: [DISCUSS] Status code for table/view rename conflicts Dmitri Bourlatchkov
  • Re: [DISCUSS] Status code for table/view rename conflicts Nándor Kollár
  • Re: [DISCUSS] Status code for table/view rename conflicts Dmitri Bourlatchkov
  • Re: [DISCUSS] Status code for table/view rename conflicts Nándor Kollár
  • Re: [DISCUSS] Status code for table/view rename conflicts Alexandre Dutra
  • Re: [DISCUSS] Status code for table/view rename conflicts Romain Manni-Bucau
  • Re: [DISCUSS] Status code for table/view rename conflicts Alexandre Dutra
  • Re: [DISCUSS] Status code for table/view rename conflicts Romain Manni-Bucau

• Earlier messages