On Tue, Jan 14, 2014 at 10:28 AM, InquiringMind <[email protected]>wrote:

> Hi, Nik.
>
> I seem to be getting very good results and getting them quickly. But I do
> notice some results like the following. Note that the query string I
> entered is the title of a book that a good friend (and B-24 navigator
> during WWII) lent me to read a couple of years ago:
>
> Search: soldiers and slaves
>
> *The page "Soldiers and slaves
> <https://en.wikipedia.org/w/index.php?title=Soldiers_and_slaves&action=edit&redlink=1>"
> does not exist. You can ask for it to be created
> <https://en.wikipedia.org/wiki/Wikipedia:Articles_for_creation>, but
> consider checking the search results below to see whether the topic is
> already covered.*
> For search help, please visit 
> Help:Searching<https://en.wikipedia.org/wiki/Help:Searching>
> .
>
>    - Soldiers and Slaves<https://en.wikipedia.org/wiki/Soldiers_and_Slaves>
>    Soldiers and Slaves: American POWs Trapped by the Nazis' Final Gamble
>    is a 2005 history of World War II by New York Times reporter Roger
>    *...*
>
>
> I am not sure why it says that there is no page, when the first response
> is exactly that page. But still, very quick and a joy to use!
>


Some stuff:
You might just be using the old search.  Right now we're deployed as a
"secondary" search engine so you have to keep re-adding the
srbackend=CirrusSearch url parameter.  Lame but I have an excuse: the point
of being a "secondary" search engine is to compare the results with the
original.  Once the index is finished building we'll make it a BetaFeature
which means if you log in you can click the "beta" tab and enable it for
all your searches.  Sorry I didn't mention it earlier.

I couldn't tell you why the old search is claiming that the page doesn't
exist.  It is more black boxy so I can't just issue my own queries against
it with something like Sense.  That has been one of the real advantages of
the Elaticsearch solution because it lets me prototype new features against
the production index really easily and it helps a ton with debugging.

We hadn't indexed that page yet so I indexed it manually and now:
https://en.wikipedia.org/w/index.php?search=soldiers+and+slaves&title=Special%3ASearch&fulltext=1&srbackend=CirrusSearch
You can see that it is the first result and you can see that we don't
highlighting "and" because it is a stop word.  At some point soon I'll be
switching to matching on both my plain analyzed copy and my stemmed/stop
worded copy so stop words will start getting highlighted.  It should look
something like:
https://en.wikipedia.org/w/index.php?title=Special%3ASearch&profile=default&search=%22soldiers+and+slaves%22&fulltext=Search&srbackend=CirrusSearch

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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1SBV0McdFDCD%3Dwwt0O%2BuSufUOvBO%2BSqR6Cm%2B4UX3U1pw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to