It seems like there are also a bunch of hacky search-alike features built
into the mediawiki database. For example, "all pages linking to this
page", "my contributions", etc. From a code cleanup standpoint, it would
also be worthwhile if these were all unified and brought together under a
single
Scott,
I was going to respond to this a while ago but couldn't really do it
justice. I'm still pretty sure my explanation won't be great, which is an
indication of just how good Google is.
For strait search there is nothing we can do that Google can't. It might
cost them more time and money to
Hi Nik,
Just a quick comment on choosing ElasticSearch over Solr:
We use Solr at Wikia, and we have a lot we can offer the Foundation in terms of
knowledge sharing. It might be a good idea to consider future opportunities to
collaborate while vetting ElasticSearch.
Even if ElasticSearch is you
I wonder if there are queries or use cases we can support that *aren't*
already better handled by google. Granted, users of private wikis can't
simply use the 'site:' trick to reuse Google search results -- but users of
private wikis also probably don't need superduper scalability.
Trying to brai
Everyone,
I'm reviving this old thread to update everyone on the status of the RFC:
We've continued working on implementation and everything seems to be
proceeding smoothly. We evaluated Elasticsearch and were super impressed
and decided it was very likely to be worth switching from Solr4 to it.
So Chad and I feel like we've gotten far enough in our prototype of our new
search backend for MediaWiki that we're ready to request comments. So here
is our format RFC:
https://www.mediawiki.org/wiki/Requests_for_comment/CirrusSearch
You'll note that the plugin is called CirrusSearch. SolrSearc