Hi,
I was about to start the release, but just saw that
https://github.com/apache/polaris/pull/2473 is a blocker for 1.1.0.
I will do a review: we should tackle that asap.
Regards
JB
On Thu, Aug 28, 2025 at 10:19 PM Dmitri Bourlatchkov wrote:
>
> Moving #2197 to 1.2.0 should be ok from my POV.
Moving #2197 to 1.2.0 should be ok from my POV.
Cheers,
Dmitri.
On Thu, Aug 28, 2025 at 1:03 AM Jean-Baptiste Onofré
wrote:
> Hii Dmitri
>
> About #2197, I think we should aim for the milestone 1.2.0 for this one.
>
> We don't have any open issue or PR for the 1.1.0 milestone, so I'm
> moving f
Hii Dmitri
About #2197, I think we should aim for the milestone 1.2.0 for this one.
We don't have any open issue or PR for the 1.1.0 milestone, so I'm
moving forward and start the release process.
Thanks !
Regards
JB
On Wed, Aug 27, 2025 at 9:49 PM Dmitri Bourlatchkov wrote:
>
> Hi All,
>
> T
Hi All,
The credential reset PR [2197] is ready to be merged. I did not want to
rush it, but if we get some more approvals soon, it might be worth
including it into 1.1.0
[2197] https://github.com/apache/polaris/pull/2197
Cheers,
Dmitri.
On Wed, Aug 27, 2025 at 8:24 AM Jean-Baptiste Onofré
wro
Hi folks,
Quick update:
1. We don't have any more pending issues for the 1.1.0 milestone, that's great !
2. We only have two pending PRs for the 1.1.0 milestone:
2.1. https://github.com/apache/polaris/pull/2341
2.2. https://github.com/apache/polaris/pull/1424
About #2341, I think it's good to be
By the way, I checked with Kostas about #1424, and he's OK to postpone
to the 1.2.0 milestone, so I'm updating the PR.
Regards
JB
On Wed, Aug 27, 2025 at 2:23 PM Jean-Baptiste Onofré wrote:
>
> Hi folks,
>
> Quick update:
> 1. We don't have any more pending issues for the 1.1.0 milestone, that'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
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
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.com/apache/polaris/issues/2436 as a 1.1 blocker, to
> request a FeatureConfiguration that gates the usage of custom s3/sts
> endpoints (apol
Thanks Dmitri
I will review the PRs.
In the meantime, I will start another PR with release blog
(highlights/release note).
Regards
JB
On Mon, Aug 25, 2025 at 1:59 AM Dmitri Bourlatchkov wrote:
>
> Hi Dennis,
>
> I opened PR [2442] to fix [2436].
>
> Please review.
>
> [2436] https://github.com
Hi Dennis,
I opened PR [2442] to fix [2436].
Please review.
[2436] https://github.com/apache/polaris/issues/2436
[2442] https://github.com/apache/polaris/pull/2442
Cheers,
Dmitri.
On Sat, Aug 23, 2025 at 12:42 AM Dmitri Bourlatchkov
wrote:
> Hi Dennis,
>
> I agree that [2436] is a valid conc
Hi Dennis,
I agree that [2436] is a valid concern and it's worth addressing before
1.1.0.
Thanks for catching it.
[2436] https://github.com/apache/polaris/issues/2436
Cheers,
Dmitri.
On Fri, Aug 22, 2025 at 11:37 PM Dennis Huo wrote:
> Filed https://github.com/apache/polaris/issues/2436 as a
Filed https://github.com/apache/polaris/issues/2436 as a 1.1 blocker, to
request a FeatureConfiguration that gates the usage of custom s3/sts
endpoints (apologies if I missed an existing FeatureConfiguration flag that
otherwise already allows service owners to provide consent or non-consent
to Cata
+1 from my end, on adding 2341 on the milestone of 1.1.0 there a couple
users in the iceberg slack for polaris too who are looking forward to this
feature
On Fri, Aug 22, 2025 at 1:14 PM Dmitri Bourlatchkov
wrote:
> Hi All,
>
> I see a user-reported issue in slack [1], which I believe is fixed
Hi All,
I see a user-reported issue in slack [1], which I believe is fixed by
[2341].
I propose to include [2341] into 1.1.0. The PR is almost ready. I
proactively added it to the 1.1.0 milestone.
WDYT?
[1]
https://apache-polaris.slack.com/archives/C084QSKD6S2/p1755892664049749?thread_ts=175579
Thanks for the summary, JB!
I do believe [608] is no longer an issue, but I'm not 100% sure. If nobody
has time to re-test it, it should be fine to defer testing it until after
1.1.0.
[608] https://github.com/apache/polaris/issues/608
Cheers,
Dmitri.
On Fri, Aug 22, 2025 at 12:44 AM Jean-Baptis
Hi folks,
I did a triage on the GH issue with the 1.1.0 milestone.
Only one issue is pending, but I think it's fixed:
https://github.com/apache/polaris/issues/608
I will test it today but if someone has an update, that would be helpful.
Regarding the PRs with the 1.1.0 milestone:
* https://githu
Hey All,
I would also request to consider getting credentials vending PR in, mostly
because a lot of users have raised this issue, for long running jobs and
are eagerly waiting for it !
Best,
Prashant Singh
On Thu, Aug 21, 2025 at 4:53 PM Dmitri Bourlatchkov
wrote:
> Hi All,
>
> Just heads up:
Hi All,
Just heads up: it looks like credential refresh config [2341] is almost
ready. I'm not advocating to hold 1.1.0 for it, but in case it is merged in
time, it would be good to mention it in release notes.
[2341] https://github.com/apache/polaris/pull/2341
Cheers,
Dmitri.
On Tue, Aug 19, 2
Hi All,
Issue [608] is currently flagged as a bug on the 1.1.0 milestone. However,
I believe it needs a thorough review now that EclipseLink is deprecated and
the JDBC persistence handles exceptions differently. Also, this report is
very old and applies to 1.0.0 and 1.0.1, yet no other users raise
I hope we can ship the CLI tool in the binary package, but nobody is
working on it. I'm OK if it goes to 1.2.
Yufei
On Wed, Aug 20, 2025 at 8:25 AM Dmitri Bourlatchkov
wrote:
> +1 to proactively updating CHANGELOG.md.
>
> That is how it was originally envisioned [1] :)
>
> [1] https://lists.ap
Hi Dennis,
Re: [2329] Option roleARN - it is optional for S3-compatible implementations
that do not require it (e.g. MinIO). It is still necessary for AWS.
Since setting it is a user's choice, I do not think a feature flag is
necessary.
[2329] https://github.com/apache/polaris/pull/2329
Cheers,
Okay, after some analysis I posted in
https://github.com/apache/polaris/issues/2325#issuecomment-3208935604 I
think it would be sufficient to fix-forward with a FeatureConfiguration
determining whether to allow skipping the roleArn so that we can preserve
fast-failure behavior in existing multi-ten
Can we also highlight the key SPI and internal-API changes that service
providers with custom plugins should be aware/reminded of at a glance?
In the future perhaps we can use a label or similar on SPI-evolution PRs to
better automate aggregating those changes, and also ideally also include
SPI ch
+1 to proactively updating CHANGELOG.md.
That is how it was originally envisioned [1] :)
[1] https://lists.apache.org/thread/qznf8toht1r7ml35lt4p8nwlk9op638v
Cheers,
Dmitri.
On Wed, Aug 20, 2025 at 6:33 AM Robert Stupp wrote:
> Thanks a lot for tackling this, Pierre!
>
> It's very difficult t
Thanks a lot for tackling this, Pierre!
It's very difficult to figure out all new features, changes and fixes
"after the fact".
I think we should establish a culture to _proactively_ populate the
content of CHANGELOG.md _within_ each applicable PR instead of asking
weeks or months later, or havin
I just opened https://github.com/apache/polaris/pull/2406 with the list of
new features that were added in main since the 1.0.x release branch was
cut. Would it be possible to get a review to ensure I did not miss any?
Note that this only contains features, and not fixes.
--
Pierre
On Wed, Au
Hi all,
Would it be possible to include the below PR in 1.1.0:
https://github.com/apache/polaris/pull/2404
This PR deprecates `ActiveRolesProvider`, thus sending a clear message
about its future removal while providing integrators with ample time
to adjust their implementations accordingly.
Rel
Hi all,
I don't see any other changes, besides what's already mentioned, that
can make it for the 1.1 "train car".
Robert
On Wed, Aug 20, 2025 at 12:26 AM Yufei Gu wrote:
>
> Hi JB,
>
> Make sense to move some enhancement and proposals to 1.2. e.g., Support for
> OpenLineage. Some of 1.1 items
Hi JB,
Make sense to move some enhancement and proposals to 1.2. e.g., Support for
OpenLineage. Some of 1.1 items have been done, we could close them. I haved
moved a few of them to 1.2.
Meanwhile, can we have a list of new things shipped with 1.1.0?
Yufei
On Tue, Aug 19, 2025 at 2:55 PM Dmitr
I'd like to merge [2401] before 1.1.0 due to Polaris behaviour changes as
noted in the PR.
Please take a look.
[2401] https://github.com/apache/polaris/pull/2401
Thanks,
Dmitri.
On Tue, Aug 19, 2025 at 3:28 PM Jean-Baptiste Onofré
wrote:
> Hi folks,
>
> We currently have 18 issues on the 1.1.
Also PR [2197] was requested [1] for inclusion into 1.1.0.
Arun: Would you be ok with deferring this PR? I personally would not want
to rush this code change into 1.1.0 as it involves authentication. At the
same time, the community follows the release train model (release what is
merged, but do no
I agree to moving enhancements and proposals to 1.2.0.
As for bugs:
[2367] - I hope to merge a fix for this one today or tomorrow.
[1901] - it may be a matter of pointing to existing docs... give me a day
to review and address it.
[552] - I believe this issue is not trivial to address. I'm not
Hi folks,
We currently have 18 issues on the 1.1.0 milestone:
https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A1.1.0
As we are now starting to have monthly releases, I propose to bump
these GH issues with improvements and proposal labels to the 1.2.0
milestone (1
36 matches
Mail list logo
