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
Move missing Mnesia-specific code to rabbit_db_* modules #6821
Conversation
a34bb4f
to
eca6557
Compare
5497aaf
to
f2efeb0
Compare
4d0ad07
to
dcd1ee8
Compare
3337f69
to
97a084c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I gave this another read through and it looks good to me. I'm not super familiar with the server codebase though so take my review with a grain of salt.
I like seeing the direct mnesia
calls and match-specs moved into db modules, it feels more clean (even independent of the upcoming khepri changes) 👍
97a084c
to
9cf10ed
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Thank you :-)
due to rabbitmq/rabbitmq-server#6821 (cherry picked from commit 72b970c)
Continuation of the work started in #6430
The idea is to isolate in those modules the code to handle the records in the database. For now, we only support Mnesia, but there is work in progress to move to another database engine. Doing this reorganization of the code will also isolate the changes of this upcoming database engine switch, making them easier to rebase and review.