Re: Filters Vs queries - for terms more than 1024

2017-07-18 Thread Kumaran Ramasubramanian
Thank you Adrien :-) On 18-Jul-2017 3:21 PM, "Adrien Grand" wrote: Sorry for the confusion, I keep saying query in all cases because queries and filters got merged in Lucene 5.0. If you are using BooleanFilter rather than BooleanQuery with Lucene 4 then things should be mostly ok if you have m

Re: Lucene GeoNear Search and Sort Performance

2017-07-18 Thread sc
David, I was able to get it working with minor changes in my codebase. I didn't have back port PointVectorStrategy class from 6.6.0 to 5.5.4 Code: final int maxNumberOfCachedQueries = 256; final long maxRamBytesUsed = 50 * 1024L * 1024L; // 50MB final QueryCache queryCach

Migration to Lucene 6.5 - Filters to Queries

2017-07-18 Thread Rilpa Jain
> Hi, > > We plan to migrate from lucene 5.5 to 6.5. We have been using > DocValuesTermsFilter extensively which was deprecated in Lucene 5.5 and > removed in Lucene 6.0. > The Javadoc specifies to use DocValuesTermsQuery and > BoolenaClause.Occur.Filter instead. However, as per our local tes

Migration to Lucene 6.5

2017-07-18 Thread Rilpa Jain
Hi, We plan to migrate from lucene 5.5 to 6.5. We have been using DocValuesTermsFilter extensively which was deprecated in Lucene 5.5 and removed in Lucene 6.0. The Javadoc specifies to use DocValuesTermsQuery and BoolenaClause.Occur.Filter instead. However, as per our local tests, the time tak

Migration to Lucene 6.5 - Queries vs Filters

2017-07-18 Thread Rilpa Jain
Hi, We plan to migrate from lucene 5.5 to 6.5. We have been using DocValuesTermsFilter extensively which was deprecated in Lucene 5.5 and removed in Lucene 6.0. The Javadoc specifies to use DocValuesTermsQuery and BoolenaClause.Occur.Filter instead. However, as per our local tests, the time tak

Unexpected scoring results

2017-07-18 Thread Jeff Wallace
On a legacy product that is still based upon Lucene-3.6.2, we (or our customers) occasionally encounter a situation like this: For what ever reason, a customer causes more than one duplicate source document to be ingested into the same index. A subsequent query whose criteria selects these duplic

Re: Filters Vs queries - for terms more than 1024

2017-07-18 Thread Adrien Grand
Sorry for the confusion, I keep saying query in all cases because queries and filters got merged in Lucene 5.0. If you are using BooleanFilter rather than BooleanQuery with Lucene 4 then things should be mostly ok if you have many clauses. But like TermsQuery, BooleanFilter always consume all match

Re: Filters Vs queries - for terms more than 1024

2017-07-18 Thread Kumaran Ramasubramanian
​Hi Adrien, Thanks for your input... 1. using boolean filters is working for even 1lakh Filter Clauses in > booleanFilter... is there any consequence using filters in this case? shall > i proceed with this? ​code snippet i used for this statement 1.. ​ for (int i = 0; i < 10 >