# Elasticsearch backend for MediaWiki
**URL:** https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467
**Category:** Elasticsearch
**Created:** [September 4, 2013, 9:26pm UTC](https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467 "2013-09-04T21:26:07Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@nik9000](https://discuss.elastic.co/u/nik9000)
#### Post date: [September 4, 2013, 9:26pm UTC](https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467/1 "2013-09-04T21:26:07Z")
Elasticsearch list,
So I've been working on a MediaWiki plugin that powers search using
Elasticsearch and you, yes you, can try it right now! All you've got to do
is head over to our handy dandy test site right here:
> **[Search results](https://test2.wikipedia.org/w/index.php?title=Special%3ASearch&profile=default&search=search+engine&fulltext=Search)**
>
> There is a page named "Search engine" on this wiki. See also the other search results found.
It is still in super alpha so I expect things to not work entirely
correctly but please let me know what you think.
The code lives here:
[https://git.wikimedia.org/summary/?r=mediawiki/extensions/CirrusSearch.git](https://git.wikimedia.org/summary/?r=mediawiki/extensions/CirrusSearch.git)
but right now it depends on stuff in the master branch of MediaWiki and
I've not been keeping the installation instructions up to date so
installing it yourself would be a pain but if you really want to let me
know and I'll help you through it.
The goal of the project is to give anyone running MediaWiki something they
can install relatively easily that will give them the same search they'd
get on Wikipedia.
Thanks,
Nik Everett
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@brian\_yoder](https://discuss.elastic.co/u/brian_yoder)
#### Post date: [September 4, 2013, 11:31pm UTC](https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467/2 "2013-09-04T23:31:17Z")
Hi, Nik,
To try this out, I entered _media_ and got 77 results. I then queried for _video
media_ and got 89 results. I expected fewer than 77, not more.
Then I queried for _video_ and got 21 results. Aha! It returned documents
that contained either _video_ or _media_.
Would have expected the default to be logical AND, not an OR. In other
words, _video media_ should return documents that contain both _video_ and \*
media\*.
The query for _video AND media_ returned only 9 documents that mentioned
both, as expected. And the query for video OR media returned all 89 results
as expected.
Just a suggestion: The default of AND and not OR is more Google/Yahoo-like
if nothing is specified. Or is this a Lucene string query quirk?
But still, very cool! And, pretty fast too! And the highlighting is
correct... Awesome!!!! Thanks for sharing!
Brian
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@nik9000](https://discuss.elastic.co/u/nik9000)
#### Post date: [September 5, 2013, 12:46am UTC](https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467/3 "2013-09-05T00:46:53Z")
On Wed, Sep 4, 2013 at 7:31 PM, InquiringMind [brian.from.fl@gmail.com](mailto:brian.from.fl@gmail.com)wrote:
> Hi, Nik,
>
> To try this out, I entered _media_ and got 77 results. I then queried for
> _video media_ and got 89 results. I expected fewer than 77, not more.
>
> Then I queried for _video_ and got 21 results. Aha! It returned documents
> that contained either _video_ or _media_.
>
> Would have expected the default to be logical AND, not an OR. In other
> words, _video media_ should return documents that contain both _video_and
> _media_.
>
> The query for _video AND media_ returned only 9 documents that mentioned
> both, as expected. And the query for video OR media returned all 89 results
> as expected.
>
> Just a suggestion: The default of AND and not OR is more Google/Yahoo-like
> if nothing is specified. Or is this a Lucene string query quirk?
This is one of the first things that came up when we started testing and I
think you are right about it but it took me some time to come around to
it. I just tried google tonight and it looked like AND was the default
operation but I recall trying it a while ago and getting results from
google that didn't include all the terms. I suppose my objections were
rooted in a love of the concept of dismax. Bah. I'll change it.
> But still, very cool! And, pretty fast too! And the highlighting is
> correct... Awesome!!!! Thanks for sharing!
Of course the highlighting is correct! Elasticsearch does highlighting
very nicely.
> Brian
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [September 5, 2013, 4:59am UTC](https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467/4 "2013-09-05T04:59:00Z")
Very cool. Congrats Nikolas!
How did you implement the "did you mean" feature? Suggest API?
--
David 馃槈
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 4 sept. 2013 脿 23:26, Nikolas Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) a 茅crit :
Elasticsearch list,
So I've been working on a MediaWiki plugin that powers search using Elasticsearch and you, yes you, can try it right now! All you've got to do is head over to our handy dandy test site right here: [https://test2.wikipedia.org/w/index.php?title=Special%3ASearch&profile=default&search=search+engine&fulltext=Search](https://test2.wikipedia.org/w/index.php?title=Special%3ASearch&profile=default&search=search+engine&fulltext=Search)
It is still in super alpha so I expect things to not work entirely correctly but please let me know what you think.
The code lives here: [https://git.wikimedia.org/summary/?r=mediawiki/extensions/CirrusSearch.git](https://git.wikimedia.org/summary/?r=mediawiki/extensions/CirrusSearch.git) but right now it depends on stuff in the master branch of MediaWiki and I've not been keeping the installation instructions up to date so installing it yourself would be a pain but if you really want to let me know and I'll help you through it.
The goal of the project is to give anyone running MediaWiki something they can install relatively easily that will give them the same search they'd get on Wikipedia.
Thanks,
## Nik Everett
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)
#### Post date: [September 5, 2013, 6:22am UTC](https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467/5 "2013-09-05T06:22:47Z")
Hi,
I do not think users really care about AND vs. OR or total hits count as
long as the first hits are relevant and lead to the information they want.
Don't try to mimic Google, you never know how it really works.
Even if you use OR you should get hits with both terms first, no? If you
use AND you can miss relevant document just because a single query term was
not analysed correctly (highly inflected languages).
Just my 2 cents.
Regards,
Luk谩拧
Dne 5.9.2013 2:47 "Nikolas Everett" [nik9000@gmail.com](mailto:nik9000@gmail.com) napsal(a):
> On Wed, Sep 4, 2013 at 7:31 PM, InquiringMind [brian.from.fl@gmail.com](mailto:brian.from.fl@gmail.com)wrote:
>
> > Hi, Nik,
> >
> > To try this out, I entered _media_ and got 77 results. I then queried
> > for _video media_ and got 89 results. I expected fewer than 77, not more.
> >
> > Then I queried for _video_ and got 21 results. Aha! It returned
> > documents that contained either _video_ or _media_.
> >
> > Would have expected the default to be logical AND, not an OR. In other
> > words, _video media_ should return documents that contain both _video_and
> > _media_.
> >
> > The query for _video AND media_ returned only 9 documents that mentioned
> > both, as expected. And the query for video OR media returned all 89 results
> > as expected.
> >
> > Just a suggestion: The default of AND and not OR is more
> > Google/Yahoo-like if nothing is specified. Or is this a Lucene string query
> > quirk?
>
> This is one of the first things that came up when we started testing and I
> think you are right about it but it took me some time to come around to
> it. I just tried google tonight and it looked like AND was the default
> operation but I recall trying it a while ago and getting results from
> google that didn't include all the terms. I suppose my objections were
> rooted in a love of the concept of dismax. Bah. I'll change it.
>
> > But still, very cool! And, pretty fast too! And the highlighting is
> > correct... Awesome!!!! Thanks for sharing!
>
> Of course the highlighting is correct! Elasticsearch does highlighting
> very nicely.
>
> > Brian
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "elasticsearch" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [September 5, 2013, 6:32am UTC](https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467/6 "2013-09-05T06:32:36Z")
+1 with Luk谩拧: i prefer having the choice as a user to enter:
search engine
+search engine
search +engine
+search +engine
By default, I'm pretty sure I will use the first in 99% as long as the more relevant come before.
My 0.01 cent in addition of Luk谩拧's 2 cents 馃槈
--
David 馃槈
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 5 sept. 2013 脿 08:22, Luk谩拧 Vl膷ek [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) a 茅crit :
> Hi,
>
> I do not think users really care about AND vs. OR or total hits count as long as the first hits are relevant and lead to the information they want. Don't try to mimic Google, you never know how it really works.
>
> Even if you use OR you should get hits with both terms first, no? If you use AND you can miss relevant document just because a single query term was not analysed correctly (highly inflected languages).
>
> Just my 2 cents.
>
> Regards,
> Luk谩拧
>
> Dne 5.9.2013 2:47 "Nikolas Everett" [nik9000@gmail.com](mailto:nik9000@gmail.com) napsal(a):
>
> > On Wed, Sep 4, 2013 at 7:31 PM, InquiringMind [brian.from.fl@gmail.com](mailto:brian.from.fl@gmail.com) wrote:
> >
> > > Hi, Nik,
> > >
> > > To try this out, I entered media and got 77 results. I then queried for video media and got 89 results. I expected fewer than 77, not more.
> > >
> > > Then I queried for video and got 21 results. Aha! It returned documents that contained either video or media.
> > >
> > > Would have expected the default to be logical AND, not an OR. In other words, video media should return documents that contain both video and media.
> > >
> > > The query for video AND media returned only 9 documents that mentioned both, as expected. And the query for video OR media returned all 89 results as expected.
> > >
> > > Just a suggestion: The default of AND and not OR is more Google/Yahoo-like if nothing is specified. Or is this a Lucene string query quirk?
> >
> > This is one of the first things that came up when we started testing and I think you are right about it but it took me some time to come around to it. I just tried google tonight and it looked like AND was the default operation but I recall trying it a while ago and getting results from google that didn't include all the terms. I suppose my objections were rooted in a love of the concept of dismax. Bah. I'll change it.
> >
> > > But still, very cool! And, pretty fast too! And the highlighting is correct... Awesome!!!! Thanks for sharing!
> >
> > Of course the highlighting is correct! Elasticsearch does highlighting very nicely.
> >
> > > ## Brian
> > >
> > > You received this message because you are subscribed to the Google Groups "elasticsearch" group.
> > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> >
> > --
> > You received this message because you are subscribed to the Google Groups "elasticsearch" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
>
> --
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@simonw\_2](https://discuss.elastic.co/u/simonw_2)
#### Post date: [September 5, 2013, 8:43am UTC](https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467/7 "2013-09-05T08:43:17Z")
On Thursday, September 5, 2013 6:59:00 AM UTC+2, David Pilato wrote:
> Very cool. Congrats Nikolas!
> How did you implement the "did you mean" feature? Suggest API?
I can answer this I guess 馃檪 - Yes that is the phrase suggester 馃檪
> --
> David 馃槈
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>
> Le 4 sept. 2013 脿 23:26, Nikolas Everett \<[nik...@gmail.com](mailto:nik...@gmail.com) \\>
> a 茅crit :
>
> Elasticsearch list,
>
> So I've been working on a MediaWiki plugin that powers search using
> Elasticsearch and you, yes you, can try it right now! All you've got to do
> is head over to our handy dandy test site right here:
> [Search results for "search engine" - test2.Wikipedia](https://test2.wikipedia.org/w/index.php?title=Special%3ASearch&profile=default&search=search+engine&fulltext=Search)
>
> It is still in super alpha so I expect things to not work entirely
> correctly but please let me know what you think.
>
> The code lives here:
> [CirrusSearch 路 extension-cirrussearch](https://git.wikimedia.org/summary/?r=mediawiki/extensions/CirrusSearch.git)
> but right now it depends on stuff in the master branch of MediaWiki and
> I've not been keeping the installation instructions up to date so
> installing it yourself would be a pain but if you really want to let me
> know and I'll help you through it.
>
> The goal of the project is to give anyone running MediaWiki something they
> can install relatively easily that will give them the same search they'd
> get on Wikipedia.
>
> Thanks,
>
> Nik Everett
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \.
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@Steve\_frank](https://discuss.elastic.co/u/Steve_frank)
#### Post date: [September 5, 2013, 11:21am UTC](https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467/8 "2013-09-05T11:21:26Z")
I would preferred this API for Mediawiki Hosting[http://www.cloudways.com/en/managed-mediawiki-cloud-hosting.php](http://www.cloudways.com/en/managed-mediawiki-cloud-hosting.php), they are good in phrase security and scalability should be the utmost
priority. Go out for Cloudways are the provide custom cloud environment
On Thursday, September 5, 2013 1:43:17 PM UTC+5, simonw wrote:
> On Thursday, September 5, 2013 6:59:00 AM UTC+2, David Pilato wrote:
>
> > Very cool. Congrats Nikolas!
> > How did you implement the "did you mean" feature? Suggest API?
>
> I can answer this I guess 馃檪 - Yes that is the phrase suggester 馃檪
>
> > --
> > David 馃槈
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> >
> > Le 4 sept. 2013 脿 23:26, Nikolas Everett [nik...@gmail.com](mailto:nik...@gmail.com) a 茅crit :
> >
> > Elasticsearch list,
> >
> > So I've been working on a MediaWiki plugin that powers search using
> > Elasticsearch and you, yes you, can try it right now! All you've got to do
> > is head over to our handy dandy test site right here:
> > [Search results for "search engine" - test2.Wikipedia](https://test2.wikipedia.org/w/index.php?title=Special%3ASearch&profile=default&search=search+engine&fulltext=Search)
> >
> > It is still in super alpha so I expect things to not work entirely
> > correctly but please let me know what you think.
> >
> > The code lives here:
> > [CirrusSearch 路 extension-cirrussearch](https://git.wikimedia.org/summary/?r=mediawiki/extensions/CirrusSearch.git)
> > but right now it depends on stuff in the master branch of MediaWiki and
> > I've not been keeping the installation instructions up to date so
> > installing it yourself would be a pain but if you really want to let me
> > know and I'll help you through it.
> >
> > The goal of the project is to give anyone running MediaWiki something
> > they can install relatively easily that will give them the same search
> > they'd get on Wikipedia.
> >
> > Thanks,
> >
> > Nik Everett
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "elasticsearch" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@nik9000](https://discuss.elastic.co/u/nik9000)
#### Post date: [September 5, 2013, 11:34am UTC](https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467/9 "2013-09-05T11:34:31Z")
On Thu, Sep 5, 2013 at 4:43 AM, simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com)wrote:
> On Thursday, September 5, 2013 6:59:00 AM UTC+2, David Pilato wrote:
>
> > Very cool. Congrats Nikolas!
> > How did you implement the "did you mean" feature? Suggest API?
>
> I can answer this I guess 馃檪 - Yes that is the phrase suggester 馃檪
Yeah, that is the phrase suggester running in always suggest mode with a
high confidence. The other trick to making the phrase suggestions good is
to split the index into two parts - one for the content pages and one for
the other pages. That way searches that only search the content pages
(most of them) only get phrase suggestions that make sense in the content
pages. If you don't do that you get suggestions based on the names of
templates which is useless to most folks.
Simonw has reviewed a few phrase suggester changes I've submitted that
should stop some of the odd responses it sometimes gives in our case.
We're not using those changes yet but will get them when we switch to
0.90.4. If I have time to do
[Suggester: Phrase suggest option to limit suggestions to exising phrases 路 Issue #3482 路 elastic/elasticsearch 路 GitHub](https://github.com/elasticsearch/elasticsearch/issues/3482) then that'll
help even more but I doubt I'll find time to get it reviewed before you cut
0.90.4 so it'll have to wait.
The search implementation currently running on wikipedia does something
pretty similar with suggestions. In many ways it was way ahead of its time
in the open source world.
Nik
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@nik9000](https://discuss.elastic.co/u/nik9000)
#### Post date: [September 5, 2013, 1:11pm UTC](https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467/10 "2013-09-05T13:11:48Z")
On Thu, Sep 5, 2013 at 2:32 AM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:
> +1 with Luk谩拧: i prefer having the choice as a user to enter:
> search engine
> +search engine
> search +engine
> +search +engine
>
> By default, I'm pretty sure I will use the first in 99% as long as the
> more relevant come before.
>
> My 0.01 cent in addition of Luk谩拧's 2 cents 馃槈
Hmmm. You guys make a compelling argument. I think I'm going to continue
with switching to AND for now because that is the least change from what
exists now. I'll keep an issue for switching to OR in the case of not
enough results. Or maybe if the user asks for it. This is the bug for the
curious: [https://bugzilla.wikimedia.org/show\_bug.cgi?id=52904](https://bugzilla.wikimedia.org/show_bug.cgi?id=52904)
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 2:18am UTC](https://discuss.elastic.co/t/elasticsearch-backend-for-mediawiki/13467/11 "2017-07-06T02:18:01Z")