Hi all,
I am usung folowing query to find exact match document with title: Abramovich says
Chelsea win showed Russian character .
In both cases with/without escaping character, and all others form
http://jakarta.apache.org/lucene/docs/queryparsersyntax.html
i recieve these exceptions:
CASE 1
I've always wondered about this too. To put it another way, how does
mergeFactor affect an IndexWriter backed by a RAMDirectory? Can I set
mergeFactor to the highest possible value (given the machine's RAM) in
order to avoid merging segments?
Kevin A. Burton [EMAIL PROTECTED] 04/20/04 04:40AM
Hi!
My Searcher's instance it not aware of changes to the index. I even create a
new instance but it seems only a complete restart does help(?):
indexSearcher = new IndexSearcher(IndexReader.open(index));
Timo
-
To
On Apr 21, 2004, at 10:01 AM, Rosen Marinov wrote:
Does it query work: my name is \Rosen\?
http://wiki.apache.org/jakarta-lucene/AnalysisParalysis
Short answer: it depends.
Questions for you to answer:
What field type and analyzer did you use during indexing? What
analyzer used with
Short answer: it depends.
Questions for you to answer:
What field type and analyzer did you use during indexing? What
analyzer used with QueryParser? What does the generated Query.toString
return?
in both cases SimpleAnalyzer
QueryParser.parse(\abc\) throws an exception and i can't see
This is not normal behaviour. Normally using a new IndexSearcher should
reflect the modified state of your index. Could you post a more
informative bit of code?
sv
On Wed, 21 Apr 2004 [EMAIL PROTECTED] wrote:
Hi!
My Searcher's instance it not aware of changes to the index. I even create a
On Wednesday 21 April 2004 19:20, Stephane James Vaucher wrote:
This is not normal behaviour. Normally using a new IndexSearcher should
reflect the modified state of your index. Could you post a more
informative bit of code?
BTW Why can't Lucene care for it itself?
Well, according to my
Normally the code should work, iif your you don't keep references to the
old Searcher (and not try cacheing it). Make sure you aren't doing this by
mistake.
For the design of your facade, you could always implement Searchable and
do the delegation to the up-to-date instance of IndexSearcher.
Gerard Sychay wrote:
I've always wondered about this too. To put it another way, how does
mergeFactor affect an IndexWriter backed by a RAMDirectory? Can I set
mergeFactor to the highest possible value (given the machine's RAM) in
order to avoid merging segments?
Yes... actually I was
Have anyone implemented any open source web crawler with Lucene? I have
a dynamic website and are looking at putting in a search tools. Your
advice is very much appreciated.
Thank you.
IMPORTANT -
This email and any attachments are confidential and may be privileged in which case
neither is
On Apr 21, 2004, at 12:17 PM, Rosen Marinov wrote:
Short answer: it depends.
Questions for you to answer:
What field type and analyzer did you use during indexing? What
analyzer used with QueryParser? What does the generated
Query.toString
return?
in both cases SimpleAnalyzer
How big is the site?
I mostly use an inhouse solution, but I've used HttpUnit for web scrapping
small sites (because of its high-level api).
Here is a hello world example:
http://wiki.apache.org/jakarta-lucene/HttpUnitExample
For a small/simple site, small modifications to this class could
12 matches
Mail list logo
