mahara-contributors team mailing list archive

[Aaron Wells <1457709@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: mahara
     Importance: Medium
     Assignee: Aaron Wells (u-aaronw)
         Status: In Progress


** Tags: elastica elasticsearch

-- 
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 ePortfolio:
  In Progress

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