mahara-contributors team mailing list archive

[Aaron Wells <1384498@xxxxxxxxxxxxxxxxxx>]

After further meditation, I think the best thing to do is what I
discussed in comment #2. We remove the search/elasticsearch plugin from
core and make it an optional plugin hosted in a separate repository.
That way we can maintain multiple versions of the plugin for multiple
versions of Elastica, and sites can just "drop in" the version that
matches their server.

The tricky part here is the process of removing it from core. We need to
support two scenarios:

1. Sites that don't use the plugin: Easy peasy, just delete all the
plugin's data from the various plugin tables, and drop the
search_elasticsearch_queue table.

2. Sites that DO use the plugin: More complicated. We don't want to
force them to reindex their site! Ideally the admin will drop in the
elasticsearch plugin as part of the upgrade, but we should also support
the case where they don't read the README and don't notice the plugin is
missing until after they do the upgrade.

2a. Admin drops in elasticsearch plugin before running the upgrade: The
code that uninstalls the elasticsearch plugin should check for the
presence of the plugin's files, and if it finds them, it assumes the
admin has chosen to manually drop in the plugin. In this case, do
nothing.

2b. Admin forgets to drop in elasticsearch plugin before running the
upgrade: What we want to do is make it possible for them to drop in the
plugin at a later date, with no data loss. There are two data loss
scenarios here. The first, is there could be unprocessed data in
search_elasticsearch_queue. So don't drop that table unless it's empty.
The second data loss scenario, is that currently the only way to get the
elasticsearch triggers to be recreated, is to press the "reindex"
button. So, we should add a separate button to just recreate the
elasticsearch triggers without also forcing a reindex.

-- 
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/1384498

Title:
  Update Elastica to version 1.3.4

Status in Mahara ePortfolio:
  Confirmed

Bug description:
  Used for elasticsearch - currently version 0.90.1

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