-
Notifications
You must be signed in to change notification settings - Fork 612
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
ISPN-12205 Add RocksDB Meta Column Family #8629
Conversation
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.
LGTM, just a note about the version checks.
|
||
MetadataImpl existingMeta = handler.loadMetadata(); | ||
if (existingMeta != null) { | ||
// TODO Perform validation/migration |
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.
Do we have a JIRA for this?
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.
Maybe for this iteration we can just verify the version and if there is a mismatch log a WARN/INFO message?
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.
Tbh as this is the first version that has this logic, I'm not sure how there could be a mismatch. It's also possible (in fact desirable) in future versions that loading from a previous major should not require migration, so logging would only add noise IMO.
// TODO Perform validation/migration | ||
} | ||
// Update the metadata entry to use the current Infinispan version | ||
handler.writeMetadata(); |
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 am not sure we want to do this if the versions don't match.
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.
My plan was that if there are any incompatibilies they will be handled via the migration logic between x
and latest version, or if this is not possible an exception is thrown before this statement is reached.
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.
Oh I agree. I am more saying in case we never get this completed. I know how some features have ideas for the future but it never comes to fruition.
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.
Ok. I've added a variable to prevent this in the meantime.
aa63889
to
f37550c
Compare
f37550c
to
f6bee24
Compare
LGTM, will press button after CI confirms. |
Integrated into master, thanks @ryanemerson ! |
https://issues.redhat.com/browse/ISPN-12205