You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polaris.apache.org by Alexandre Dutra <ad...@apache.org> on 2025/10/28 16:53:51 UTC
[DISCUSS] Remove legacy management endpoints
Hi all,
The legacy management endpoints (health and metrics) were deprecated
in the last release.
I therefore would like to propose to remove them completely in the
next release (1.3).
The PR was open a long time ago:
https://github.com/apache/polaris/pull/2276
What do you all think of this plan?
Thanks,
Alex
Re: [DISCUSS] Remove legacy management endpoints
Posted by Alexandre Dutra <ad...@apache.org>.
Hi all,
The PR was merged, FYI.
Thanks,
Alex
On Mon, Nov 3, 2025 at 3:21 PM Alexandre Dutra <ad...@apache.org> wrote:
>
> Hi all,
>
> I am going to merge the PR by EOD.
>
> Thanks,
> Alex
>
> On Mon, Nov 3, 2025 at 1:33 PM Robert Stupp <sn...@snazy.de> wrote:
> >
> > Hi all,
> >
> > Just wanted to note that the CHANGELOG for the 1.2.0 release already
> > mentions "The legacy management endpoints at `/metrics` and
> > `/healthcheck` have been deprecated in 1.2.0 and will be completely
> > removed in 1.3.0 or in 2.0.0 (whichever happens earlier).".
> >
> > Robert
> >
> > On Tue, Oct 28, 2025 at 6:28 PM Dmitri Bourlatchkov <di...@apache.org> wrote:
> > >
> > > Hi Alex,
> > >
> > > Thanks for reviving that PR!
> > >
> > > I agree that removing lenacy management endpoints is reasonable at this
> > > time.
> > >
> > > As I also mentioned in GH, management endpoints are different from normal
> > > API in that they are used by devops / admin users, not "clients". The admin
> > > users should be able to switch to the new management endpoints at any time
> > > before the next release and without affecting end users.
> > >
> > > Cheers,
> > > Dmitri.
> > >
> > > On Tue, Oct 28, 2025 at 12:54 PM Alexandre Dutra <ad...@apache.org> wrote:
> > >
> > > > Hi all,
> > > >
> > > > The legacy management endpoints (health and metrics) were deprecated
> > > > in the last release.
> > > >
> > > > I therefore would like to propose to remove them completely in the
> > > > next release (1.3).
> > > >
> > > > The PR was open a long time ago:
> > > >
> > > > https://github.com/apache/polaris/pull/2276
> > > >
> > > > What do you all think of this plan?
> > > >
> > > > Thanks,
> > > > Alex
> > > >
Re: [DISCUSS] Remove legacy management endpoints
Posted by Alexandre Dutra <ad...@apache.org>.
Hi all,
I am going to merge the PR by EOD.
Thanks,
Alex
On Mon, Nov 3, 2025 at 1:33 PM Robert Stupp <sn...@snazy.de> wrote:
>
> Hi all,
>
> Just wanted to note that the CHANGELOG for the 1.2.0 release already
> mentions "The legacy management endpoints at `/metrics` and
> `/healthcheck` have been deprecated in 1.2.0 and will be completely
> removed in 1.3.0 or in 2.0.0 (whichever happens earlier).".
>
> Robert
>
> On Tue, Oct 28, 2025 at 6:28 PM Dmitri Bourlatchkov <di...@apache.org> wrote:
> >
> > Hi Alex,
> >
> > Thanks for reviving that PR!
> >
> > I agree that removing lenacy management endpoints is reasonable at this
> > time.
> >
> > As I also mentioned in GH, management endpoints are different from normal
> > API in that they are used by devops / admin users, not "clients". The admin
> > users should be able to switch to the new management endpoints at any time
> > before the next release and without affecting end users.
> >
> > Cheers,
> > Dmitri.
> >
> > On Tue, Oct 28, 2025 at 12:54 PM Alexandre Dutra <ad...@apache.org> wrote:
> >
> > > Hi all,
> > >
> > > The legacy management endpoints (health and metrics) were deprecated
> > > in the last release.
> > >
> > > I therefore would like to propose to remove them completely in the
> > > next release (1.3).
> > >
> > > The PR was open a long time ago:
> > >
> > > https://github.com/apache/polaris/pull/2276
> > >
> > > What do you all think of this plan?
> > >
> > > Thanks,
> > > Alex
> > >
Re: [DISCUSS] Remove legacy management endpoints
Posted by Robert Stupp <sn...@snazy.de>.
Hi all,
Just wanted to note that the CHANGELOG for the 1.2.0 release already
mentions "The legacy management endpoints at `/metrics` and
`/healthcheck` have been deprecated in 1.2.0 and will be completely
removed in 1.3.0 or in 2.0.0 (whichever happens earlier).".
Robert
On Tue, Oct 28, 2025 at 6:28 PM Dmitri Bourlatchkov <di...@apache.org> wrote:
>
> Hi Alex,
>
> Thanks for reviving that PR!
>
> I agree that removing lenacy management endpoints is reasonable at this
> time.
>
> As I also mentioned in GH, management endpoints are different from normal
> API in that they are used by devops / admin users, not "clients". The admin
> users should be able to switch to the new management endpoints at any time
> before the next release and without affecting end users.
>
> Cheers,
> Dmitri.
>
> On Tue, Oct 28, 2025 at 12:54 PM Alexandre Dutra <ad...@apache.org> wrote:
>
> > Hi all,
> >
> > The legacy management endpoints (health and metrics) were deprecated
> > in the last release.
> >
> > I therefore would like to propose to remove them completely in the
> > next release (1.3).
> >
> > The PR was open a long time ago:
> >
> > https://github.com/apache/polaris/pull/2276
> >
> > What do you all think of this plan?
> >
> > Thanks,
> > Alex
> >
Re: [DISCUSS] Remove legacy management endpoints
Posted by Dmitri Bourlatchkov <di...@apache.org>.
Hi Alex,
Thanks for reviving that PR!
I agree that removing lenacy management endpoints is reasonable at this
time.
As I also mentioned in GH, management endpoints are different from normal
API in that they are used by devops / admin users, not "clients". The admin
users should be able to switch to the new management endpoints at any time
before the next release and without affecting end users.
Cheers,
Dmitri.
On Tue, Oct 28, 2025 at 12:54 PM Alexandre Dutra <ad...@apache.org> wrote:
> Hi all,
>
> The legacy management endpoints (health and metrics) were deprecated
> in the last release.
>
> I therefore would like to propose to remove them completely in the
> next release (1.3).
>
> The PR was open a long time ago:
>
> https://github.com/apache/polaris/pull/2276
>
> What do you all think of this plan?
>
> Thanks,
> Alex
>