+1 for the summary, agreed to simplify the approach to avoid partial schema
creation/update at this point.
Yufei
On Tue, Aug 5, 2025 at 12:39 AM Alexandre Dutra wrote:
> Hi all,
>
> Trying to summarize the opinions we've got so far:
>
> 1) On the server side:
>
> - Decouple schema setup and bo
Hello again!
The PR has been merged, make sure to rebase if you have any ongoing work.
Thanks,
Alex
On Tue, Aug 5, 2025 at 2:39 PM Robert Stupp wrote:
>
> +1 from mv POV to merge
>
> On Tue, Aug 5, 2025 at 1:58 PM Alexandre Dutra wrote:
> >
> > Hello all,
> >
> > We would like to merge [2233]
Hi,
I can contribute what we did in Nessie:
S3 request signing requires one additional request against the catalog
for each request performed by S3 (HTTP/REST here). The catalog has to
enforce the access rules (allow-listing, allowed read & write
locations).
Doing the access privilege "dance" con
+1 from mv POV to merge
On Tue, Aug 5, 2025 at 1:58 PM Alexandre Dutra wrote:
>
> Hello all,
>
> We would like to merge [2233] sooner than later. Is it OK to merge today?
>
> Thanks,
> Alex
>
> [2233] https://github.com/apache/polaris/pull/2233
>
> On Fri, Aug 1, 2025 at 2:18 PM Alexandre Dutra
Hello all,
We would like to merge [2233] sooner than later. Is it OK to merge today?
Thanks,
Alex
[2233] https://github.com/apache/polaris/pull/2233
On Fri, Aug 1, 2025 at 2:18 PM Alexandre Dutra wrote:
>
> Hi all,
>
> Here is the PR:
>
> https://github.com/apache/polaris/pull/2233
>
> Thanks,
Hi all,
Trying to summarize the opinions we've got so far:
1) On the server side:
- Decouple schema setup and bootstrap
- Schema setup should be off by default (opt-in)
- Schema setup should use "defaults"
- Schema setup is rather for tests or evaluation (=> production
readiness warning?)
2) On
