Hello.
I tried with
doc.add(new Field("contents",line,Field.Store.YES,Field.Index.ANALYZED));
The BooleanQuery/PrefixMatch/WildCard all started Running fine..
But it broke the Existing code for Phrase Suggestion/InfixSuggester. Now
these suggesters are returning Word suggestion instead of Phr
Just returned from a vacation and getting back to this. I am trying to
understand why filters can be faster when the filter is used only once.
From what I've read, it looks like filters give performance gains when
cached and called repeatedly. Also, since they build a bit set for the
entire list
Hi there
I am using Lucene 4.4, and i am hitting cpu usage limitations on my core
i7 windows 7 64bit box. Seems like the IO system(ssd) has still
capacity, but when running 8 threads searching on the index in parallel,
all logical cpu cores are at 100% usage.
Is there a common way available
Hello. We've just upgraded to 4.3.1 from 2.9.2 and are having a problem
with native ordering of search results.
We always want documents returned in order of "rank", which for us is a
float value that we assign to each document at index time. Rank depends
in whether, for example, the item is
Thank you Duke for your help. We have already tried that solution
after a kindly advise from this mailing list. But we still having
the error.
Actually the POM of the project is here
http://lesimisped.free.fr/servo/pom2.xml. It reuses a project which
uses Lucene,
The link
http://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html#ServicesResourceTransformer
will
help.
Best regards,
Duke
If not now, when? If not me, who?
On Mon, Aug 19, 2013 at 8:48 PM, Amal Kammoun wrote:
> Dear All,
>
> Please do you have any advice regardin
