Hi,
You have to reopen all the underlying DirectoryReaders and then build a new
MultiReader. MultiReader has no idea about commit points and therefore cannot
reopen. The reopen of MultiReader worked for most cases in 3.6, but it was just
buggy.
In any case: I would use ReaderManager to keep the
Hi,
Thank you Uwe. I see mostly ConstantScoreQuery, BooleanQuery and
FilteredQuery. Maybe it is quite cheap for MI but I execute quite many
queries on it and I was looking for optimizations.
--
Paweł
On Mon, Jun 30, 2014 at 3:01 PM, Uwe Schindler wrote:
> Hi,
>
> Queries have to be rewritten,
Hi,
I'm migrating from Lucene 3.6.1 to 4.3.0.
I used to have indexer for data in each month and wrapped with one
*MultiReader*.
Behind the multireader, I have ScheduledExecutorService thread keep
reopening the sub-readers in certain interval time. And I got one searcher
for the multireader.
Index
Hi,
Queries have to be rewritten, this has nothing to do with scoring. What type of
queries are you seeing this? Wildcard or text ranges are expensive, there is no
way around, but for MemoryIndex (I assume you mean this class), this should be
quite cheap.
-
Uwe Schindler
H.-H.-Meier-Allee
Hi,
I'm running queries over memory index and see in profiler significant CPU
usage on method createNormalizedWeight. Most of the time is spent on
rewrite method.
Is it any way to avoid it or optimize to reduce CPU usage on
createNormalizedWeight? Scoring is not important for me at all. It only
wa
