Hi All, PR [3760] has been in review for quite some time and has received a couple of approvals already.
If there are no fresh comments / concerns I propose merging on Feb 27. Many thanks to Sung for driving this refactoring! Note: The proposed SPI change may be considered "breaking" in some contexts, but it perfectly aligns with the standing Polaris evolution guidelines [1]. Adapting to the SPI change in downstream builds is trivial. This PR does not require any functional changes. [1] https://polaris.apache.org/in-dev/unreleased/evolution/ [3760] https://github.com/apache/polaris/pull/3760 On Sun, Feb 15, 2026 at 2:19 PM Sung Yun <[email protected]> wrote: > Hi folks, > > First of all, thanks so much for the feedback on the RFC[1], mailing > list[2], and draft PR. Based on the community support for this > refactoring, I’ve opened a PR[3] that introduces the new > PolarisAuthorizer SPI surface (AuthorizationState / > AuthorizationRequest / AuthorizationDecision, authorizeDecision + > authorizeOrThrow overloads) and adds selective resolution via > PolarisResolutionManifest.resolveSelections(...). This PR only > introduces the new SPI/API surface and does not change existing > handler or authorization behavior. > > I’ve also created a tracking issue[4] that outlines the full > multi‑phase plan so we can track the subsequent changes needed to > complete the refactoring. > > I’d appreciate a review on the PR so we can kick off this refactoring work. > > PR: https://github.com/apache/polaris/pull/3760 > > Thank you! > > Cheers, > Sung > > [1] RFC: https://docs.google.com/document/d/1OaiQG_C4- > yUe0ihaDBxtw_mEcOOzUBnWPazzVbjQi5U/edit?tab=t.0#heading=h.dyow25dt9w1 > [2] Prior mailing list discussion: > https://lists.apache.org/thread/o420khg3f68lrhslz8t8qbop72dn1blj > [3] PR: https://github.com/apache/polaris/pull/3760 > [4] Tracking Issue: https://github.com/apache/polaris/issues/3779 >
