Просмотр исходного кода

feat(release): Adds btree index on `Release` version (#31243)

* feat(release): Adds btree index on Release version

Adds a btree index on field `version` of model
`Release` to be able to perform prefix search on
release names

* Rename index name
Ahmed Etefy 3 лет назад
Родитель
Сommit
5f259ad7c7

+ 1 - 1
migrations_lockfile.txt

@@ -6,5 +6,5 @@ To resolve this, rebase against latest master and regenerate your migration. Thi
 will then be regenerated, and you should be able to merge without conflicts.
 
 nodestore: 0002_nodestore_no_dictfield
-sentry: 0266_add_dashboard_widget_detail_field
+sentry: 0267_sentry_release_version_btree
 social_auth: 0001_initial

+ 39 - 0
src/sentry/migrations/0267_sentry_release_version_btree.py

@@ -0,0 +1,39 @@
+# Generated by Django 2.2.24 on 2022-01-21 09:04
+
+from django.db import migrations, models
+
+from sentry.new_migrations.migrations import CheckedMigration
+
+
+class Migration(CheckedMigration):
+    # This flag is used to mark that a migration shouldn't be automatically run in production. For
+    # the most part, this should only be used for operations where it's safe to run the migration
+    # after your code has deployed. So this should not be used for most operations that alter the
+    # schema of a table.
+    # Here are some things that make sense to mark as dangerous:
+    # - Large data migrations. Typically we want these to be run manually by ops so that they can
+    #   be monitored and not block the deploy for a long period of time while they run.
+    # - Adding indexes to large tables. Since this can take a long time, we'd generally prefer to
+    #   have ops run this and not block the deploy. Note that while adding an index is a schema
+    #   change, it's completely safe to run the operation after the code has deployed.
+    is_dangerous = True
+
+    # This flag is used to decide whether to run this migration in a transaction or not. Generally
+    # we don't want to run in a transaction here, since for long running operations like data
+    # back-fills this results in us locking an increasing number of rows until we finally commit.
+    atomic = False
+
+    dependencies = [
+        ("sentry", "0266_add_dashboard_widget_detail_field"),
+    ]
+
+    operations = [
+        migrations.AddIndex(
+            model_name="release",
+            index=models.Index(
+                fields=["organization", "version"],
+                name="sentry_release_version_btree",
+                opclasses=["", "text_pattern_ops"],
+            ),
+        ),
+    ]

+ 7 - 0
src/sentry/models/release.py

@@ -465,6 +465,13 @@ class Release(Model):
             ("organization", "date_added"),
             ("organization", "status"),
         )
+        indexes = [
+            models.Index(
+                fields=["organization", "version"],
+                opclasses=["", "text_pattern_ops"],
+                name="sentry_release_version_btree",
+            )
+        ]
 
     __repr__ = sane_repr("organization_id", "version")