Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
From: Rilpa Jain <rilpa25@gmail.com>
Content-Type: multipart/alternative;
	boundary=Apple-Mail-98611BF1-4EF3-40EE-9D84-94E402EF97DE
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Tue, 18 Jul 2017 16:14:11 -0400
Subject: Migration to Lucene 6.5 - Filters to Queries
Message-Id: <7039874B-25E2-414C-9965-BACB991EA1B3@gmail.com>
References: <A597E46153D8A042ACBFAB96DC848FD07ED94049@USOPWYMBX01.nyoffice.tradeweb.com>
To: java-user@lucene.apache.org
archived-at: Tue, 18 Jul 2017 20:48:06 -0000

--Apple-Mail-98611BF1-4EF3-40EE-9D84-94E402EF97DE
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable


> Hi,
> =20
> We plan to migrate from lucene 5.5 to 6.5. We have been using DocValuesTer=
msFilter extensively which was deprecated in Lucene 5.5 and removed in Lucen=
e 6.0.
> The Javadoc specifies to use DocValuesTermsQuery and BoolenaClause.Occur.Fi=
lter instead. However, as per our local tests, the time taken to search docu=
ments has increased with this change.
> =20
> Below is one of the scenarios in our application -
> We do a search within a search.
> =20
> (Before migration to Lucene 5.5)
> The first search is on a text field with discrete values. (There is no pat=
tern to the value of this text field. Here the terms[] ranges from 1 to 200k=
 in size.)  =E2=80=93 We use DocValuesTermsFilter and pass it is as Filter p=
arameter to search method.
> 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 se=
arch method.
> =20
> (After migration to Lucene 6.5)
> The first search is on a text field with discrete values. (There is no pat=
tern to the value of this text field. Here the terms[] ranges from 1 to 200k=
 in size.)  =E2=80=93 We use DocValuesTermsQuery and add it to BooleanQuery w=
ith Occur.Filter.
> The second search is on result of step 1- This could be either a TermQuery=
 or NumericRangeQuery added to BooleanQuery with Occur.MUST.
> The booleanQuery is build and passed to search method.
> =20
> This query execution after migration takes 5x-10x times more as compared t=
o using DocValuesTermsFilter.
> =20
> Is there a better class to generate query in our scenario than the one use=
d above? Or is there anything that I am missing?
> Any insights would help! Thanks.

--Apple-Mail-98611BF1-4EF3-40EE-9D84-94E402EF97DE--