how to use explain function！

Hi,all.Please give me some example to use explain function.I want to know detail information about compute weight and Score. thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Apostrophe S ('s)

Sam Giffney wrote: Using the Standard Analyzer the string McDonald's is indexed with the term mcdonald so it will be found by a (QueryParser parsed) query for McDonald or McDonald's but not McDonalds Wikipedia (who uses lucene) says on http://en.wikipedia.org/wiki/Wikipedia:Searching An apostr

Apostrophe S ('s)

Using the Standard Analyzer the string McDonald's is indexed with the term mcdonald so it will be found by a (QueryParser parsed) query for McDonald or McDonald's but not McDonalds Wikipedia (who uses lucene) says on http://en.wikipedia.org/wiki/Wikipedia:Searching An apostrophe is identical to

Re: Singleton and IndexModifier

On 8/20/06, lude <[EMAIL PROTECTED]> wrote: Hello, when using the new IndexModifier of Lucene 2.0, what would be the best creation-pattern? Should there be one IndexModifier instance in the application (==singelton)? Could an IndexModifier be opened for a longer time or should it be created on

Singleton and IndexModifier

Hello, when using the new IndexModifier of Lucene 2.0, what would be the best creation-pattern? Should there be one IndexModifier instance in the application (==singelton)? Could an IndexModifier be opened for a longer time or should it be created on use and immediately closed? Another issue: -

Re: Exception raised when searching with sorting on an empty index.

On 8/18/06, Mathias Herberts <[EMAIL PROTECTED]> wrote: When doing a search with sorting on a field (ts) on the MultiSearcher with an empty RAM based index, an exception is thrown saying: no terms in field ts - cannot determine sort type If you specify the type of sort you want, this shouldn't

Re: Search Performance Problem 16 sec for 250K docs

The index is already built in date order i.e. the older documents appear first in the index, what i am trying to achieve is however the latest documents appearing first in the search results .. without the sort .. i think they appear by relevance .. well thats what it looked like .. I am looking

Re: Search Performance Problem 16 sec for 250K docs

Talk about mails crossing in the aether.. wrote my resonse before seeing the last two... Sounds like you're on track. Erick On 8/20/06, Erick Erickson <[EMAIL PROTECTED]> wrote: About luke... I don't know about command-line interfaces, but if you copy your index to a different machine and

Re: Search Performance Problem 16 sec for 250K docs

About luke... I don't know about command-line interfaces, but if you copy your index to a different machine and use Luke there. I do this between Linux and Windows boxes all the time. Or, if you can mount the remote drive so you can see it, you can just use Luke to browse to it and open it up. You

Re: Search Performance Problem 16 sec for 250K docs

Just ran some tests .. it appears that the problem is in the sorting .. i.e. //hits = searcher.search(query, new Sort("sid", true));-> 17 secs //hits = searcher.search(query, new Sort("sid", false)); -> 17 secs hits = searcher.search(query);-> less than 1 sec .. am trying something out

Re: Search Performance Problem 16 sec for 250K docs

This is why a warming strategy like Solr takes is very valuable. The searchable index is always serving up requests as fast as Lucene works, which is achieved by warming a new IndexSearcher with searches/ sorts/filter creating/etc before it is swapped into use. Erik On Aug 20, 200

Re: Search Performance Problem 16 sec for 250K docs

Ok I get your point, this still however means the first search on the new searcher will take a huge amount of time .. given that this is happening now .. i.e. new search -> new query -> get hits ->20+ secs .. this happens every 5 mins or so .. although subsequent searches may be quicker .. Am