Hi all,
If you haven't been following along with development, we're working on replacing MWSearch/lsearchd with CirrusSearch (powered by Elasticsearch). Nik and I been working on this for the last several weeks and now it's ready for wider testing outside of labs.
This is invitation for you to play with some totally alpha software and report all kinds of bugs you may find. So hop on over to https://test2.wikipedia.organd mess around with Special:Search and the API's list search and prefix search.
When testing this, it's useful to compare results from the old and new engines. I added some query parameters that let you toggle between them. Just add srbackend=LuceneSearch|CirrusSearch to force one or the other.
All bugs can be filed in BZ under the CirrusSearch component[0]. Depending on how things go, we'd like to roll this out for mw.org on the 28th. Happy bug hunting :D
-Chad
[0] https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions&...
Wait, Elasticsearch? I thought the original discussions were about Solr?
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]
On 2013-08-15 5:07 PM, Chad wrote:
Hi all,
If you haven't been following along with development, we're working on replacing MWSearch/lsearchd with CirrusSearch (powered by Elasticsearch). Nik and I been working on this for the last several weeks and now it's ready for wider testing outside of labs.
Original discussions were with Solr. We evaluated both and went with Elastic. The Solr attempt is in the 'solr' branch on the git repo.
-Chad
On Thu, Aug 15, 2013 at 5:09 PM, Daniel Friesen daniel@nadir-seen-fire.comwrote:
Wait, Elasticsearch? I thought the original discussions were about Solr?
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]
On 2013-08-15 5:07 PM, Chad wrote:
Hi all,
If you haven't been following along with development, we're working on replacing MWSearch/lsearchd with CirrusSearch (powered by Elasticsearch). Nik and I been working on this for the last several weeks and now it's ready for wider testing outside of labs.
On Thu, Aug 15, 2013 at 8:09 PM, Daniel Friesen daniel@nadir-seen-fire.comwrote:
Wait, Elasticsearch? I thought the original discussions were about Solr?
It certainly started that way but there were but some rather insistent folks talked me in to giving Elasticsearch a chance. I spent a week putting together a prototype and I was so impressed that I convinced us to move over. I'm reasonably sure I sent out an email at the time. I know I updated the RFC. In any case, that is where we are.
As far what impressed me about elasticsearch: I like the documentation. I like the query syntax. I like the fully baked schema api. I (mostly) liked the source code itself. i like the deb package. I like how organized the bug submission and contribution process is. Seriously, if you are running an open source project, build something like http://www.elasticsearch.org/contributing-to-elasticsearch/ . Forcing the user to reproduce bugs with curl is genius for a service like elasticsearch.
So, yeah, we started with solr but didn't stay there.
Nik
On Thu, Aug 15, 2013 at 8:09 PM, Daniel Friesen daniel@nadir-seen-fire.comwrote:
Wait, Elasticsearch? I thought the original discussions were about Solr?
Chad wrote:
Original discussions were with Solr. We evaluated both and went with Elastic. The Solr attempt is in the 'solr' branch on the git repo.
On 08/15/2013 08:42 PM, Nikolas Everett wrote:
It certainly started that way but there were but some rather insistent folks talked me in to giving Elasticsearch a chance. I spent a week putting together a prototype and I was so impressed that I convinced us to move over. I'm reasonably sure I sent out an email at the time. I know I updated the RFC. In any case, that is where we are.
As far what impressed me about elasticsearch: I like the documentation. I like the query syntax. I like the fully baked schema api. I (mostly) liked the source code itself. i like the deb package. I like how organized the bug submission and contribution process is. Seriously, if you are running an open source project, build something like http://www.elasticsearch.org/contributing-to-elasticsearch/ . Forcing the user to reproduce bugs with curl is genius for a service like elasticsearch.
So, yeah, we started with solr but didn't stay there.
Nik
Nik, Chad, thanks for the explanation!
Daniel, the July monthly WMF engineering report https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2013/July and previous monthly engineering reports included summaries of where the search investigation was going. You can read more specifically about search at https://www.mediawiki.org/wiki/Search and https://www.mediawiki.org/wiki/Search/status . Hope that helps.
wikitech-l@lists.wikimedia.org