NoSQL database agnostic persistence #1189
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mostly complete proposal for the database agnostic persistence layer to support NoSQL databases in Apache Polaris.
This PR is intended to illustrate the “whole spiel” and contains all necessities. Smaller, easier reviewable PRs will be opened soon for some of the areas covered in this PR to initially enable MongoDB persistence.
The overall approach borrows the architectural approach from Nessie to isolate database specifics from higher level concerns.
The most important objective for the implementation is correctness, especially in scenarios with high concurrent load. Explicit tests to verify the correctness are included, for the CI “use case” and for manual/special runs against a clustered database setup (which are just “too much” for the Github hosted runners).
The current integration point is
MetaStoreManagerFactory/PolarisMetaStoreManagerimplemented in the “bridge” Gradle project.See
components/persistence/README.mdin this PR for more technical information.To run Polaris w/ the “dummy” in-memory “database”:
To run Polaris against MongoDB: