mahara-contributors team mailing list archive

[Mahara Bot <1457709@xxxxxxxxxxxxxxxxxx>]

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

commit a02be21a1d70a6866ae2964b647440682a7af2d5
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date:   Wed Jul 15 13:26:24 2015 +1200

Remove the index name from elasticsearch JSON data (Bug 1457709)

If we remove the index name from the JSON data, then Elasticsearch
will just use the index name in the URL path, which we're already
setting correctly.

Doing it this way, we don't have to rely on the Elasticsearch server
setting the "rest.action.multi.allow_explicit_index: false" flag.

Change-Id: Ib6194b89e68d539a7959b9e12ec1ac9e3528dd27

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

Title:
  Elasticsearch plugin doesn't work with URL-based access control

Status in Mahara:
  Fix Committed

Bug description:
  We changed the Elasticsearch plugin to use the _bulk command to load
  data into Elasticsearch. But this poses problems for hosting setups
  that are using URL-based access control, as described here:
  https://www.elastic.co/guide/en/elasticsearch/reference/1.x/url-
  access-control.html

  This is because the way Elastica handles the _bulk command, it puts
  the index name into the request body: localhost/_bulk, instead of
  localhost/index/_bulk

  Elasticsearch *can* handle the indexname in the URL for _bulk
  commands. But we'll need to patch Elastica to handle it.

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