Hi everyone
this vote passed with the following result:
+1 (binding): JB Onofré, Ryan Blue, Kent Yao
+1 (non binding): Robert Stupp, Dmitri Bourlatchkov, Ed Espino
I'm completing the release.
Thanks everyone for your vote!
Regards
JB
On Wed, Jul 30, 2025 at 9:51 AM Jean-Baptiste Onofré wrote
Hi Michael,
I'm not sure I completely understand your point about explicit vs. implicit.
>From my POV, existing Apache Polaris code is always explicit since it is
available for inspection end-to-end, injection points are annotated and
injection behaviour is controlled by explicit configuration.
Hi All,
I propose to add [1] a new feature flag PURGE_VIEWS_ON_DROP to allow
dropping views when DROP_WITH_PURGE_ENABLED is false (default).
The default value of PURGE_VIEWS_ON_DROP is true to match prior behaviour.
Any concerns?
[1] https://github.com/apache/polaris/pull/2369
Thanks,
Dmitri.
Thanks Dennis for listing these SPIs. To make it easy for developer to
understand, I think we have multiple options
1. Annotation-based approach, Apache Spark adopts it, e.g., @Stable,
@@Experimental. It is fine-grained, but it brings a lot of maintenance
costs. For example, which interfaces shoul
Possibly a point with mentioning, then, is that dependencies must be
explicit in order to be clear about where there’s an extension contract.
Some of the CDI work has led to things being less clear as things that were
explicitly passed around are now simply @Injected whenever they’re needed.
That m
Hi all,
I just figured out that there is a chance of running into OOMs when
purging tables. Even if an OOM does not occur, there is a huge amount
of heap pressure that deserves broader attention.
TL;DR all manifest-files are materialized on heap at once as base-64
encoded strings (~ +33%) on the
