Hi All,
We have a Lucene 3.6-based index set which is quite large and currently in use.
What will be the upgrade path to (a) 4.x or (b) 5.x? With respect to the data
migration, etc. What are the steps and is it technically possible? I read that
3.x to 5.x is not possible, and throws IndexTooStal
Hi Mike,
Thanks for the very prompt and clear response. We look forward to using the new
(new for us) Lucenene goodies :-)
Clive
From: Michael McCandless
To: Lucene Users ; kiwi clive
Sent: Thursday, May 28, 2015 2:34 AM
Subject: Re: Search Performance with NRT
As long as you cal
Dear Real-time Java Community,
Remi and I are pleased to announce the release of the JTRES 2015 call for
papers (below) and the JTRES 2015 website: http://jtres2015.univ-mlv.fr. JTRES
will be held in Paris on October 7th and 8th. We hope to see you there and
look forward to your submissi
As long as you call SM.maybeRefresh from a dedicated refresh thread
(not from a query's thread) it will work well.
You may want to use a warmer so that the new searcher is warmed before
becoming visible to incoming queries ... this ensures any lazy data
structures are initialized by the time a que
Hi,
I am facing an issue with phrase query having special character (like &, dot,
comma, : etc). I have tried following queries and although there were data, 0
result returned.
1) Search Query --> name:"Pep:Trans vaccines, GSK" Parsed Query -->
+name:"pep:trans vaccines gsk"
Result r
Hi Guys
We are considering changing our Lucene indexer / search architecture from 2
separate JVMs to a single one to benefit from the very latest index views NRT
readers provide.
In the past we cached our IndexSearchers to avoid cold searches every time and
reopened them periodically. In the
