Thread:Extension talk:CirrusSearch/Cirrus behaving like standard search?/reply (2)

Hi! You can see the way we've configured Cirrus for enwiki at http://en.wikipedia.org/w/api.php?action=cirrus-config-dump&srbackend=CirrusSearch&format=json. For the most part its close to the defaults except for enabling some elasticsearch plugins. You can also have a look at the Jenkins.php file in Cirrus for how the integration tests are configured. You shouldn't copy it directly because it contains some hacks to make testing faster but it contains whatever configuration we expect the integration tests to work for.

For the specific questions: 1. Did you mean: it certainly should work. Its based on term frequency and has some hard cutoffs like "don't show a did you mean if there is a redirect from Canad to Canada". Try adding ?cirrusDumpQuery=yes to the search and see if it contains "suggest" in the json. That is the "is it plugged in" test. 2. Phrase matching:  We do check for matching phrases. It might be worth getting the query from ?cirrusDumpQuery=yes (its the query part of the json), checking for the rescore portion, and then sending it directly to Elasticsearch with the explain parameter and posting both in a pastebin thing. Its something that works for us and in the regression tests so I'm sure its fixable. 3. Elasticsearch 1.1.1: That is a pretty old version. We're on 1.3.something and even that it pretty old. One thing you have to do if you upgrade is to turn on dynamic scripting and make sure Elasticsearch is firewalled off from everyone you don't want running scripts. Its something we'd like to fix in Cirrus but haven't had the time. 4. What version of Cirrus are you using? I've tried to make a few backports to the 1.22 branch but its been a while. git commit hash is really the best way to identify Cirrus versions unfortunately.