-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Deprecate Legacy Migration System #8121
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.
One small cleanup comment
|
||
// todo (cgardens) - this method is deprecated. new migrations are not run using this code path. it | ||
// is scheduled to be removed. | ||
final Optional<AirbyteVersion> airbyteDatabaseVersion = runFileMigration( |
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.
Nit, we can remove runFileMigration
as well.
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.
According to the description, this PR is trying to just remove the least amount of code possible to stop the migration from being run, so runFileMigration()
will be removed in a future PR
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 see, I forgot the description. I checked it in IntelliJ and it is thew only place where it got called, I believe that we can remove this dead code in this review safely. IMO since it is the only place this method is call we should remove it in the same review.
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.
Please don't consider it as a blocker.
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.
@benmoriceau yeah. it is intentional. in case we've made a mistake and need to bring it back by removing just the call point the chance of having a complex merge conflict on revert is lower, which is why i have taken this approach. if you're okay with that can you switch your review so that gh won't block the PR?
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 ok, I just hope that doing that will lead to a lot of dead code If we do it too often. As far as we make sure it is clean up, that's fine.
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 for a minimal change to remove the file migration call
My only concern is that it according to this slack message, it sounds like a user was able to upgrade from <0.32.0, straight to v0.32.1, which may indicate that the logic to prevent this is not working correctly? If so, we probably should not merge this change until that is fixed |
looking into the issue that @lmossman raised before merging it. |
3636583
to
1ebc923
Compare
2bc7fc2
to
0f43bf6
Compare
add env file to properties test rename util class add test for read resource as file better comment on log line class blank space do not call run file migration from server app clean
1ebc923
to
d207118
Compare
confirmed that this looked good after doing a test minor version bump here. |
closes #6917
What
How
ServerApp.java