Persistence model built around implementation details

[snazy]

Describe the bug

The persistence model (as in org.apache.polaris.core.entity) is built around assumptions for a particular implementation. It does not just define different entity types (think: catalog, namespace, table, etc) but also implementation details about cache and data consistency details. These details leak though the whole code base that has to deal with any kind of entity. This makes it extremely difficult to use another persistence backend than the one this persistence model was built for, like the "simpler KV store" mentioned in PolarisMetaStoreSession.

To Reproduce

No response

Actual Behavior

No response

Expected Behavior

No response

Additional context

No response

System information

No response

[collado-mike]

This is potentially an improvement, not a bug

[snazy]

This is potentially an improvement, not a bug

I disagree, because this effectively prevents the intention of the abstraction to have pluggable storage even for "simpler KV stores", as defined in the Polaris-internal API.