Skip to content

chore(aci): pending delete WorkflowFireHistory rollout columns #91910

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

Merged
merged 1 commit into from
May 20, 2025

Conversation

cathteng
Copy link
Member

Follow up to #91904

Set the unused columns to pending deletion according to https://develop.sentry.dev/backend/application-domains/database-migrations/#deleting-columns

@cathteng cathteng requested review from a team as code owners May 19, 2025 22:39
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label May 19, 2025
# is a schema change, it's completely safe to run the operation after the code has deployed.
# Once deployed, run these manually via: https://develop.sentry.dev/database-migrations/#migration-deployment

is_post_deployment = False
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this table has 43 mil rows. should this and/or the follow up migration to actually delete the columns be post deploy?

Copy link
Member Author

@cathteng cathteng May 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's not being written to very often anymore (kind of exploded last week, but that change has been rolled back and updated to only write for workflows that fire actions)

Copy link
Member

@vgrozdanic vgrozdanic May 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this table has 43 mil rows. should this and/or the follow up migration to actually delete the columns be post deploy?

Nope, neither of them should be post deployment.

We have it in our docs, but it is a bit hidden, column removals should never be post deployment operations: https://develop.sentry.dev/backend/application-domains/database-migrations/#post-deploy-migrations-is_post_deployment

Copy link
Contributor

This PR has a migration; here is the generated SQL for src/sentry/workflow_engine/migrations/0063_drop_rollout_workflowfirehistory_columns.py

for 0063_drop_rollout_workflowfirehistory_columns in workflow_engine

--
-- Moved workflowfirehistory.has_fired_actions field to pending deletion state
--
-- (no-op)
--
-- Moved workflowfirehistory.has_passed_filters field to pending deletion state
--
-- (no-op)

Copy link

codecov bot commented May 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

⚠️ Parser warning

The parser emitted a warning. Please review your JUnit XML file:

Warning while parsing testcase attributes: Limit of string is 1000 chars, for name, we got 2083 at 1:157237 in /home/runner/work/sentry/sentry/.artifacts/pytest.junit.xml
Additional details and impacted files
@@           Coverage Diff           @@
##           master   #91910   +/-   ##
=======================================
  Coverage   87.62%   87.63%           
=======================================
  Files       10356    10357    +1     
  Lines      587133   587137    +4     
  Branches    22585    22585           
=======================================
+ Hits       514493   514512   +19     
+ Misses      72212    72197   -15     
  Partials      428      428           

@cathteng cathteng merged commit f8a7613 into master May 20, 2025
61 checks passed
@cathteng cathteng deleted the cathy/aci/remove-wfh-rollout-cols-pending branch May 20, 2025 15:15
@github-actions github-actions bot locked and limited conversation to collaborators Jun 5, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants