Skip to content
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

Remove references to and ignore good_jobs.retried_good_job_id column #1430

Merged
merged 1 commit into from
Jul 16, 2024

Conversation

bensheldon
Copy link
Owner

No description provided.

@bensheldon bensheldon added the refactor Code changes that do not introduce new features label Jul 16, 2024
@bensheldon bensheldon force-pushed the remove-retried_good_job_id branch from a7f919b to 4735c22 Compare July 16, 2024 18:17
@bensheldon bensheldon force-pushed the remove-retried_good_job_id branch from 4735c22 to 02c4738 Compare July 16, 2024 18:38
@bensheldon bensheldon marked this pull request as ready for review July 16, 2024 20:18
@bensheldon bensheldon merged commit 76450c5 into main Jul 16, 2024
14 checks passed
@bensheldon bensheldon deleted the remove-retried_good_job_id branch July 16, 2024 20:18
@jgarber623
Copy link

Apologies if this is noted somewhere, but:

If I'm reading the changes here correctly, are retried_good_job_id (and is_discrete, it seems) slated for removal (or able to be removed) from the database schema? Stated differently, is a migration forthcoming that drops them?

Based on the description in #1427, I'm also guessing the changes here are v4 refactor related?

@bensheldon
Copy link
Owner Author

@jgarber623 no worries!

If I'm reading the changes here correctly, are retried_good_job_id (and is_discrete, it seems) slated for removal (or able to be removed) from the database schema? Stated differently, is a migration forthcoming that drops them?

Yes, eventually. I think I added them to ignored_columns but apparently not in this PR 🤔 I think I may need to wait until v5 to actually drop the columns because it's not possible to guarantee that the release with the ignored columns has been deployed before the migrations are run. So I'm imagining a major version cycle.

@jgarber623
Copy link

@bensheldon Thanks for the explanation and quick reply! Much appreciated.

Totally makes sense not to add a migration yet to drop those columns. That'd definitely be worth documenting in a major version upgrade guide (like you have with v3 to v4) since it's (maybe? likely?) a destructive irreversible action.

Thanks again for the clarification. 🙌🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactor Code changes that do not introduce new features
Projects
Development

Successfully merging this pull request may close these issues.

2 participants