XJDKC commented on PR #1899: URL: https://github.com/apache/polaris/pull/1899#issuecomment-2977353404
> @XJDKC I'm a bit concerned about updating the representation of entities, because those represent the _persisted_ state. Maybe an opportunity to abstract such concerns from persistence? Hey @snazy, it's possible with this framework: we can define new `TransformationPoint` called `CATALOG_PRE_LOAD` and dynamically apply a transformer to inject the service identity info. But I think different vendor may have different opinions about this question. i.e. It's good to persist the service identity info since it must be very unlikely to be changed. e.g. Users create a federated polaris catalog, get Polaris assigned service identity info for this catalog entity, then configure their IAM role's trust policy to allowlist polaris service identity. However, later on, polaris uses a different service identity info to access users' Glue Catalog, it will break this Catalog Entity. So I think we should let the service vendor to choose the behavior, WDYT? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@polaris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
