mahara-contributors team mailing list archive

[Mahara Bot <1479543@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/5108
Committed: https://git.nzoss.org.nz/mahara/mahara/commit/47728fe119c678aa684887373984a91d2d26842f
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch:    master

commit 47728fe119c678aa684887373984a91d2d26842f
Author: Robert Lyon <robertl@xxxxxxxxxxxxxxx>
Date:   Sat Aug 15 09:16:59 2015 +1200

Bug 1479543: Making sure the last run shows correct total

When updating the artefact table with new 'path' option

Change-Id: I6f236f53e907cb4f686c8973c9a98502fc0186ed
Signed-off-by: Robert Lyon <robertl@xxxxxxxxxxxxxxx>

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1479543

Title:
  Upgrading from 1.9 to 15.04 in mysql can timeout on big sites

Status in Mahara:
  Fix Committed
Status in Mahara 1.10 series:
  In Progress
Status in Mahara 15.04 series:
  In Progress

Bug description:
  If there are lots of artefact and elasticsearch is running then the
  adding of the 'path' column and updating all the artefacts to have new
  path value can cause very long upgrade, or even upgrade timing
  out/locking up the database.

  The problem is that there is a trigger on the artefact table - but as
  the path value is not stored by elasticsearch we don't need to get
  elasticsearch to reindex all the artefact rows.

  So we will drop the trigger for this bit and re-add the trigger after
  the artefact table has add it's path column added.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1479543/+subscriptions