0fc9f9d3e7
DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
40 lines
1 KiB
Ruby
40 lines
1 KiB
Ruby
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class ScheduleEventMigrations < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
BUFFER_SIZE = 1000
|
|
|
|
disable_ddl_transaction!
|
|
|
|
class Event < ActiveRecord::Base
|
|
include EachBatch
|
|
|
|
self.table_name = 'events'
|
|
end
|
|
|
|
def up
|
|
jobs = []
|
|
|
|
Event.each_batch(of: 1000) do |relation|
|
|
min, max = relation.pluck('MIN(id), MAX(id)').first
|
|
|
|
if jobs.length == BUFFER_SIZE
|
|
# We push multiple jobs at a time to reduce the time spent in
|
|
# Sidekiq/Redis operations. We're using this buffer based approach so we
|
|
# don't need to run additional queries for every range.
|
|
BackgroundMigrationWorker.bulk_perform_async(jobs)
|
|
jobs.clear
|
|
end
|
|
|
|
jobs << ['MigrateEventsToPushEventPayloads', [min, max]]
|
|
end
|
|
|
|
BackgroundMigrationWorker.bulk_perform_async(jobs) unless jobs.empty?
|
|
end
|
|
|
|
def down
|
|
end
|
|
end
|