My application also meet this problem last year and I researched on the code
and found the reason.
The whole process is as follow:
1. When using NRTCachingDirectory, it will use RAMDirectory as cache and
MMapDirectory as delegate. The new segment will be created in the process of
flush or merge
Hi Wang,
would it be possible to open a JIRA issue so we can track this?
In any case, I would recommend to disable compound files if you use
NRTCachingDirectory (as a workaround).
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> ---
Hi Uwe,
I already created the issue in JIRA
"https://issues.apache.org/jira/i#browse/LUCENE-5800";.
Zhijiang Wang
--发件人：Uwe
Schindler 发送时间：2014年7月1日(星期二) 15:47收件人：java-user
; wangzhijiang999 主
题：RE: 答复：RE: RE:
Hi,
I wanted to know of the best approach to follow if a few fields in my indexed
documents are changing at run time (after index and before or during search),
but a majority of them are created at index time.
I could see the JIRA given below but it is scheduled for Lucene 4.9, I believe.
T
Hi,
Is there any way to pre-build rewritten queries and cache them somewhere.
When I have a set of queries which is used very frequently I would get
significant boost (10-20% of CPU wasted) when I can skip rewriting (for
example by caching rewritten queries).
Thank you for any suggestions.
On Mon
This JIRA is "complicated", don't really expect it in 4.9 as it's
been hanging around for quite a while. Everyone would like this,
but it's not easy.
Atomic updates will work, but you have to stored="true" for all
source fields. Under the covers this actually reads the document
out of the stored f
Except that Lucene now offers efficient numeric and binary DocValues
updates. See IndexWriter.updateNumeric/Binary...
On Jul 1, 2014 5:51 PM, "Erick Erickson" wrote:
> This JIRA is "complicated", don't really expect it in 4.9 as it's
> been hanging around for quite a while. Everyone would like th
Hi Shai,
So one follow-up question.
Assume that my use case is to have approx. ~50M documents indexed with each
document having about ~10-15 indexed but not stored fields. These fields will
never change, but there are another ~5-6 fields that will change and will
continue to change after the i
