collado-mike opened a new pull request, #417:
URL: https://github.com/apache/polaris/pull/417

   # Description
   
   `PolarisMetaStoreManager` is a monolithic interface that captures 
persistence, storage credential vending, remote cache, and grant management. 
This makes it easy to tie together many things that shouldn't be tied together 
- for example, the authorizer has dependencies on the cache types, so that it's 
impossible to make authorization pluggable using different grant rules.
   
   This change strictly splits up the interface into multiple interfaces, but 
the single `PolarisMetaStoreManager` is still an extension of the others. Where 
it is possible to refer to specific interfaces, (e.g., the Resolver and the 
EntityCache), the references are changed, but we don't have factory types to 
generate realm-specific implementations of all interfaces and the PR was 
growing far too large when I started on that path.
   
   Future PRs would update components to refer to specific interfaces and to 
break the tie between the PolarisMetaStoreManager interface and the others. The 
PolarisMetaStoreManagerImpl may continue to implement all interfaces.
   
   Fixes # (issue)
   
   ## Type of change
   
   Please delete options that are not relevant.
   
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [ ] Documentation update
   - [X] New feature (non-breaking change which adds functionality)
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to not work as expected)
   - [ ] This change requires a documentation update
   
   # How Has This Been Tested?
   
   Interface only change - all existing tests continue to pass.
   
   **Test Configuration**:
   * Hardware:
   * Toolchain:
   * SDK:
   
   # Checklist:
   
   Please delete options that are not relevant.
   
   - [X] I have performed a self-review of my code
   - [X] I have commented my code, particularly in hard-to-understand areas
   - [ ] I have made corresponding changes to the documentation
   - [X] My changes generate no new warnings
   - [ ] If adding new functionality, I have discussed my implementation with 
the community using the linked GitHub issue
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to