Fix integer columns on new VSA table

This migration replaces the analytics_cycle_analytics_issue_stage_events
with a version where bigints are used.

Changelog: changed

db/migrate/20210903054158_recreate_stage_issue_events_table_with_bigints.rb

+# frozen_string_literal: true
+
+class RecreateStageIssueEventsTableWithBigints < Gitlab::Database::Migration[1.0]
+  include Gitlab::Database::PartitioningMigrationHelpers::TableManagementHelpers
+
+  def up
+    drop_table :analytics_cycle_analytics_issue_stage_events # rubocop:disable Migration/DropTable
+
+    execute <<~SQL
+    CREATE TABLE analytics_cycle_analytics_issue_stage_events (
+      stage_event_hash_id bigint NOT NULL,
+      issue_id bigint NOT NULL,
+      group_id bigint NOT NULL,
+      project_id bigint NOT NULL,
+      milestone_id bigint,
+      author_id bigint,
+      start_event_timestamp timestamp with time zone NOT NULL,
+      end_event_timestamp timestamp with time zone,
+      PRIMARY KEY (stage_event_hash_id, issue_id)
+    ) PARTITION BY HASH (stage_event_hash_id)
+    SQL
+
+    create_hash_partitions :analytics_cycle_analytics_issue_stage_events, 32
+  end
+
+  def down
+    drop_table :analytics_cycle_analytics_issue_stage_events
+
+    execute <<~SQL
+    CREATE TABLE analytics_cycle_analytics_issue_stage_events (
+      stage_event_hash_id integer NOT NULL,
+      issue_id integer NOT NULL,
+      group_id integer NOT NULL,
+      project_id integer NOT NULL,
+      milestone_id integer,
+      author_id integer,
+      start_event_timestamp timestamp with time zone NOT NULL,
+      end_event_timestamp timestamp with time zone,
+      PRIMARY KEY (stage_event_hash_id, issue_id)
+    ) PARTITION BY HASH (stage_event_hash_id)
+    SQL
+
+    create_hash_partitions :analytics_cycle_analytics_issue_stage_events, 32
+  end
+end

db/schema_migrations/20210903054158

+113d6bb813a89646d48c8ba6a86fc8e73f741d5c345f603bfe33939fb90f9428
\ No newline at end of file