s perform worse than legacy
> numeric fields: exact queries on low-cardinality fields. But if you
> perform actual range queries on high-cardinality fields, you should
> see improvements.
>
> On Thu, Apr 4, 2019 at 7:45 AM brahmam wrote:
> >
> > Hi
> >
> > Than
ou might want to look into going
> straight to Lucene 8.0 (latest).
>
> On Wed, Apr 3, 2019 at 9:04 AM brahmam wrote:
> >
> > Hi,
> >
> > Thanks for your response.
> >
> > Does the IndexUpgrader tool will help in order to re-index using
> LongPoint ?
&
Adrien Grand wrote:
> You got it right, you will need to reindex with LongPoint before being
> about to search with LongPoint#newRangeQuery. It's fine to keep using
> LegacyNumericRangeQuery until then.
>
> On Tue, Apr 2, 2019 at 1:56 PM brahmam wrote:
> >
> > Hi,
smooth migration to one next major version,
so now migrating to 6.6.5 from 5.5.3 can be made smooth with the help of
existing API changes alone in 6.6.5 ? any guidance on this will be helpful.
Thanks in advance!
On Tue, 2 Apr 2019, 14:36 Adrien Grand, wrote:
> Hi Brahmam,
>
> T
LongPoint.newRangeQuery() only.
thank you in advance!
On Tue, Apr 2, 2019 at 9:37 AM brahmam wrote:
> Hi,
>
> The main idea to migrate to 6.6.5(not to 7.6.x) from 5.5.3 is to have
> smooth upgrade by avoiding re-indexing of the data at this point of time.
>
> Coming to the issue of not
.org/solr/UsingMailingLists
>
> Best,
> Erick
>
> > On Mar 27, 2019, at 10:39 PM, brahmam wrote:
> >
> > Hi Team,
> >
> > we want to migrate from lucene 5.5.3 to 6.6.5.
> > We see after upgraded to 6.6.5 we are not able to search the existing
Hi Team,
we want to migrate from lucene 5.5.3 to 6.6.5.
We see after upgraded to 6.6.5 we are not able to search the existing
data(which was managed with 5.5.3), are we missing anything here during
upgrade?
--
Thanks & Regards,
Sree
Hi,
Any guidance on the above points 2&3 will greatly help us to proceed with
lucene 7 migration. Thank you in advance!
Regards,
Sreeram
On Thu, 14 Feb 2019, 05:45 brahmam Hi Thank you for sharing the details.
>
> 1) Is NumericRangeQuery is the only API removed in license 7 wh
n its internal implementation).
>
> Uwe
>
> -
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: brahmam
> > Sent: Monday, February 11, 2019 7:10 AM
> >
Hi,
We want to migrate from lucene 5.5.3 to 7.6.0(current stable version).
Could you please help with migration guide if any available for the same?
*One of the scenario observed:*
when used *NumericRangeQuery.newLongRange, *we can pass the precision step
as the parameter.
But now in 7.6.0, we ne
10 matches
Mail list logo
