Yes, I am only calling IndexWriter.addDocument()
Interestingly, relative performance of either approach seems to greatly
depend on the number of documents per index. In both types of runs, I used
10 writer threads, each writing documents with the same set of fields (but
random values), into its ow
Hi,
I am getting the following OOM consistently whenever the index is opened . Is
it because now the index is holding too many terms ? Our application ( that has
Lucene 2.9.3 ) already has reached 1.8G of virtual memory.
Is there a way I can avoid OOM during IndexReader open because of too many
64% greater index size when you merge at the end is odd.
Can you post the ls -l output of the final index in both cases?
Are you only adding (not deleting) docs?
This is perfectly valid to do... but I'm surprised you see the two
approaches taking about the same time. I would expect letting Luce
Hi,
We are hiring multiple Lucene/Solr engineers, tech leads, architects based
in Minneapolis - both full time and consulting for developing new search
platform.
Please reach out to me - svamb...@gmail.com
Thanks,
Venkat Ambati
Sr. Manager, Best Buy
Any takers on this one or is my inquiry a bit too broad? I can post my
test code if that helps...
On Tue, May 29, 2012 at 6:42 PM, Vitaly Funstein wrote:
> Hello,
>
> I am trying to optimize the process of "warming up" an index prior to
> using the search subsystem, i.e. it is guaranteed that no
You'll have to be more specific about what you mean by "fuzzy phrase
search".
Even in the classic Lucene query parser "sloppy phrase search is
supported" - variable spacing between terms.
LUCENE-2754 added support for all multi-term queries (which includes
FuzzyQuery) for spans, so you could
Did you find any solution for this.
I am looking for similar solution, please let me know if you found any useful
info regarding fuzzy phrase search inlucene.
Thanks & Regards,
Harish B.N.
Lead Software Engineer
Thomson Reuters
Phone: +91-80-67193219
Mobile: +91-9845807294
harish...@thomsonreut
