My point is that if we do not include realm ID in the Primary Key (option
1), then we're effectively forcing all users to deploy Polaris with a
DataSource per Realm approach. I do not see how we can decouple this
concern from the JDBC schema. Any subsequent schema changes will complicate
upgrades.
Hey
1. I'm unsure why the Resolver was written to assume no role means all
roles. But I think it has to do with
2. The Resolver was intended to be able to resolve principal roles, grants,
and target entities all at one "snapshot" based on the entity and grant
versions returned by that loadEntities
Hey All,
Based on our recent discussion and the PR feedback, it seems like we need
more in-depth conversations to align on the best path forward.
Considering this, I'd like to propose we decouple this particular feature
from the current JDBC implementation.
My reasoning for this suggestion is as
Thanks Pierre for driving this. The plan sounds good to me! A side
question, are we planning to make a benchmark pipeline against the main
branch? The only backend option now is the EclipseLink, we will have the
JDBC backend soon.
Yufei
On Fri, Apr 18, 2025 at 9:54 AM Pierre Laporte
wrote:
> H
