Hi Dennis,
Looking at the existing config ALLOW_EXTERNAL_TABLE_LOCATION, how does this
fit into the model you've outlined? It does not support storing tables at
UUID locations. The new config added in the linked PR is analogous to this
existing config.
If a user wants to store tables at random(iz
It seems we're very loosely mixing/interchanging three distinct concepts
both here and in the PR, and we need to make sure to clarify which topic is
applicable in the code being added and in the bug report.
Reposting from my PR comment:
The original design was always to still securely support a s
heads up: the Credential refresh (config) PR [2341] LGTM. If there are no
more comments, I propose to merge tomorrow.
[2341] https://github.com/apache/polaris/pull/2341
Cheers,
Dmitri.
On Tue, Aug 26, 2025 at 3:28 AM Jean-Baptiste Onofré
wrote:
> Hi
>
> I propose to have tomorrow as deadline f
Hi JB,
This plan sounds good to me.
I moved [608] to the 1.2.0 milestone (it was discussed before). I believe
this was the last remaining issue in 1.1.0.
[608] https://github.com/apache/polaris/issues/608
Cheers,
Dmitri.
On Tue, Aug 26, 2025 at 3:28 AM Jean-Baptiste Onofré
wrote:
> Hi
>
> I
I've merged PR 2442, which fixes 2436.
Cheers,
Dmitri.
On Mon, Aug 25, 2025 at 1:39 AM Jean-Baptiste Onofré
wrote:
> Hi Dennis
>
> I agree, let's include 2436 in the 1.1.0 release.
>
> Thanks !
> Regards
> JB
>
> On Sat, Aug 23, 2025 at 5:36 AM Dennis Huo wrote:
> >
> > Filed https://github.co
Hi everyone,
Thank you to all who shared their perspectives on this topic. As of end of day
August 25, 2025, there are no outstanding or blocking objections raised in this
thread. This indicates that we have reached community consensus on the proposed
direction. Accordingly, the window for stru
Update: I added a production readiness check.
Kostas
On Tue, Aug 26, 2025 at 2:11 PM Kostas Zoumpatianos <
kostas.zoumpatia...@fivetran.com> wrote:
> Thank you Alexandre and Jean-Baptiste for your comments!
>
> So, if I could summarize the concerns they are the following:
> 1. Personally identif
Thank you Alexandre and Jean-Baptiste for your comments!
So, if I could summarize the concerns they are the following:
1. Personally identifiable (sensitive) information. As Alexandre said this
could become an issue once we get into federated principals territory.
2. OOMs, DOS attacks and metric d
Hi
I propose to have tomorrow as deadline for PRs to include in
1.1.0-incubating: everything not blocker will be bump to
1.2.0-incubating (thanks to your monthly release cycle).
Thanks!
Regards
JB
On Mon, Aug 25, 2025 at 7:38 AM Jean-Baptiste Onofré wrote:
>
> Hi Dennis
>
> I agree, let's inclu
