-
Notifications
You must be signed in to change notification settings - Fork 220
[DRAFT] NoSQL database agnostic persistence #1189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
snazy
wants to merge
7
commits into
apache:main
Choose a base branch
from
snazy:persistence-nosql
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
71814d8
to
c12b122
Compare
499528e
to
be15e39
Compare
This was referenced Mar 20, 2025
fba1990
to
b332065
Compare
b332065
to
51f58c5
Compare
acdb182
to
feac6b6
Compare
b05911d
to
641bbb4
Compare
7eadb1a
to
5936c9d
Compare
Log explicit messages around auto-bootstrapping and unnecessary/left-over secrets that are (still) available.
Provides an abstraction to submit asynchronous tasks, optionally with a delay or delay + repetition and implementations based on Java's `ThreadPoolExecutor` and Vert.X.
Provides a framework and implementations for unique ID generation, including a monotonically increasing timestamp/clock source. Includes a [Snowflake-IDs](https://medium.com/@jitenderkmr/demystifying-snowflake-ids-a-unique-identifier-in-distributed-computing-72796a827c9d) implementation.
5936c9d
to
7b29903
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
/PolarisMetaStoreManager
implemented in the “bridge” Gradle project.See
components/persistence/README.md
in this PR for more technical information.To run Polaris w/ the “dummy” in-memory “database”:
To run Polaris against MongoDB: