Providing special characters in input when using QueryParser.

2013-09-09 Thread Ankit Murarka
Hello, I am using StandardAnalyzer for indexing all the documents. While Searching say for Boolean/Wildcard/Prefix query, I am using *QueryParser* for the user supplied input. But when I supply / as an input along with some characters like: \ I get a lexcial error due to presence of

Re: Strange performance of Lucene 4.4.0

2013-09-09 Thread Mirko Sertic
Ok, using Sort.INDEXORDER for default sorting is blazing fast. Just for my understanding, what is the difference between both methods? Is just unneccesary score computation the problem of the CPU peak? Thanks in advance Mirko Am 09.09.2013 13:43, schrieb Michael McCandless: Sort.INDEXORDER, o

Re: Re: Re: Re: Strange performance of Lucene 4.4.0

2013-09-09 Thread Michael McCandless
Sort.INDEXORDER, or, just make your own Collector, which should be faster than INDEXORDER. Mike McCandless http://blog.mikemccandless.com On Mon, Sep 9, 2013 at 7:19 AM, Mirko Sertic wrote: > Dear Mike > > I need an API to disable Scoring without any sorting. > > Unfortunately every method in

Aw: Re: Re: Re: Strange performance of Lucene 4.4.0

2013-09-09 Thread Mirko Sertic
Dear Mike I need an API to disable Scoring without any sorting. Unfortunately every method in IndexSearcher where i can say doDocScores also require a not-null Sort instance. So what would be the best way to disable scoring and have no sorting, and archiving the same performance as the "Empty

Re: Re: Re: Strange performance of Lucene 4.4.0

2013-09-09 Thread Michael McCandless
If new Sort() fails to sort by score, that's a bug! Can you please open a Jira issue? Mike McCandless http://blog.mikemccandless.com On Mon, Sep 9, 2013 at 5:21 AM, Mirko Sertic wrote: > Hi > > Basically i am running a load test. For every run i executed about 1 million > queries on the same

Aw: Re: Re: Strange performance of Lucene 4.4.0

2013-09-09 Thread Mirko Sertic
Hi Basically i am running a load test. For every run i executed about 1 million queries on the same index with the same query string, so it should be warmed up very well ;-) It performs about 8x faster with an empty Sort() instance than the first option. Still do not get it. An empty Sort insta

Re: Aw: Re: Strange performance of Lucene 4.4.0

2013-09-09 Thread Toke Eskildsen
On Sun, 2013-09-08 at 15:15 +0200, Mirko Sertic wrote: > I have to check, but my usecase does not require sorting or even > scoring at all. I still do not get what the difference is... Please describe how you perform your measurements. How do you ensure that the index is warmed equally for the two