Hi Huaxin
Thank you so much for starting this thread.
I gonna take a look: at first glance it looks good to me, especially
because it's not a "breaking" change thanks to the header.
Let me review the doc.
Thanks again,
Regards
JB
On Thu, Sep 11, 2025 at 1:37 PM huaxin gao wrote:
>
> Hi all,
>
Hi folks,
this vote passed with the following result:
+1 (binding): John D. Ament, JB Onofré, Ed Espino
+1 (non binding): Dmitri Bourlatchkov, Alex Dutra, Pierre Laporte,
Romain Manni-Bucau
The podling will do the release announcement.
Thanks everyone for your vote!
Regards
JB
On Thu, Sep 11,
Hi,
I agree with Yufei:
1. I would announce EclipseLink will be removed in 1.3
2. We do remove it in the 1.3 release
3. I don't think we need any tool: moving from EclipseLink to JDBC
should be smooth and with minimal effort. For one shot effort, not
sure it's worth to spend time on "migration too
Hi all,
Thanks for the responses - and sorry for the delay, the past few weeks have
been quite busy.
I agree with all the points presented.
* I will start a vote soon for the following endpoints, once I have a draft PR
that shows the proposed changes: createCatalog, createPrincipalRole,
creat
+1 on removing it. Given Polaris’ monthly release cadence, it seems fine to
wait two (remove in 1.3) or three (remove in 1.4) more releases.
https://github.com/apache/polaris-tools/tree/main/polaris-synchronizer can
migrate principals, but doesn't support policies.
I’m not sure it’s worth buildin
You are right, Russell. We should make a clear migration path, so our
EclipseLink users are able to easily transition off on EclipseLink. I know
that this has come up before [1]. Let me investigate a few options on what
guidance we can give or what tooling we can produce.
[1] https://github.com/ap
We have two migration tools:
* https://github.com/apache/polaris-tools/tree/main/iceberg-catalog-migrator
* https://github.com/apache/polaris-tools/tree/main/polaris-synchronizer
I'm pretty confident that iceberg-catalog-migrator works well, but it can
only migrate tables, not principals.
I nev
I meant in AWS being able to use IAM authentication instead of username and
password.
I did a bit of digging and deployed Polaris and Postgres in Minikube.
For what I can see, Polaris in order to connect to Postgres needs the
connection details in a k8 secret file.
This is the object
{"relation
Hi folks,
Gentle reminder about this release.
Thanks !
Regards
JB
On Thu, Sep 11, 2025 at 3:36 AM Jean-Baptiste Onofré wrote:
>
> Hi everyone,
>
> The Apache Polaris community has voted and approved the release of
> Apache Polaris 1.1.0-incubating (rc0). We are now kindly asking the
> IPMC memb
+1 I think removing EclipseLink should happen soon now that we have 2
releases with it deprecated. I have
looked too deeply into this but do we have a migration plan for users
already on EclipseLink to get over to the
JDBC Impl?
On Wed, Sep 17, 2025 at 12:53 PM Dmitri Bourlatchkov
wrote:
> Thank
Sorry, I forgot a 3rd PR, also already approved:
3) Remove ActiveRolesProvider
https://github.com/apache/polaris/pull/2390
Thanks,
Alex
On Tue, Sep 16, 2025 at 7:16 PM Alexandre Dutra wrote:
>
> Hi all,
>
> The following 2 PRs related to authentication have been waiting for a while
> now:
>
>
Thanks for bringing this issue up, Adam!
I support removing EclipseLink code immediately.
My rationale:
* Due to EclipseLink deprecation, non-trivial new features are not
necessarily implemented there [1]
* Any new bugs reported for EclipseLink are not likely to get attention
because this backe
Howdy Polaris Community!
I was going through our open bugs and I noticed that there are around 5 to
10 bugs related to EclipseLink persistence. I was wondering when we
believe a good time to remove EclipseLink would be.
Personally, I think we could probably start doing it now since it's been
depr
13 matches
Mail list logo
