Re: Migration to Lucene 6.5

2017-07-27 Thread Adrien Grand
00k in size.) - We use DocValuesTermsFilter and pass it is as Filter > parameter to search method. > 2. The second search is on result of step 1- This could be either a > TermQuery or NumericRangeQuery, evaluated to query and added as query > parameter to search method. > >

Migration to Lucene 6.5 - Filters to Queries

2017-07-18 Thread Rilpa Jain
NumericRangeQuery, evaluated to query and added as query parameter to search > method. > > (After migration to Lucene 6.5) > The first search is on a text field with discrete values. (There is no > pattern to the value of this text field. Here the terms[] ranges from 1 to > 2

Migration to Lucene 6.5

2017-07-18 Thread Rilpa Jain
method. (After migration to Lucene 6.5) 1. The first search is on a text field with discrete values. (There is no pattern to the value of this text field. Here the terms[] ranges from 1 to 200k in size.) - We use DocValuesTermsQuery and add it to BooleanQuery with Occur.Filter. 2. The

Migration to Lucene 6.5 - Queries vs Filters

2017-07-18 Thread Rilpa Jain
method. (After migration to Lucene 6.5) 1. The first search is on a text field with discrete values. (There is no pattern to the value of this text field. Here the terms[] ranges from 1 to 200k in size.) - We use DocValuesTermsQuery and add it to BooleanQuery with Occur.Filter. 2. The