Automatic Prefix Query

2011-09-26 Thread Michael Szediwy
Hi, is it possible to convert a query like "un lis" to "un* lis*" automatically using lucene API? Thanks in advance for your answer. Cheers Michael - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For addition

Re: Automatic Prefix Query

2011-09-26 Thread Erick Erickson
You could break the input stream up and construct a BooleanQuery from a series of PrefixQuerys, but there's nothing automatic that I know of. Best Erick On Mon, Sep 26, 2011 at 5:30 AM, Michael Szediwy wrote: > Hi, > > is it possible to convert a query like "un lis" to "un* lis*" > automatically

RE: Automatic Prefix Query

2011-09-26 Thread Uwe Schindler
Hi, You can subclass QueryParser and override newFieldQuery to produce a PrefixQuery instead of TermQuery - that's all. Here a simple example with an anonymous inner class: qp = new QueryParser(...) { @Override protected Query newTermQuery(Term term) { return new PrefixQuery(term); } };

RE: Automatic Prefix Query

2011-09-26 Thread Uwe Schindler
One thing to mention: > You can subclass QueryParser and override newFieldQuery to produce a > PrefixQuery instead of TermQuery - that's all. Here a simple example with an > anonymous inner class: > > qp = new QueryParser(...) { > @Override > protected Query newTermQuery(Term term) { > re

LuceneTaxonomyWriter unexpected shutdown

2011-09-26 Thread Mihai Caraman
Something strange happened, with no error what-so-ever. Ran a taxwriter in parallel with a IndexWriter, but because the indexReader was NearRealTime, i reopened taxwriter and refreshed the taxreader every 3min. day one, OK day two, OK day tree, no more indexing, results were only from the previou

Possible partial update of a document?

2011-09-26 Thread Zhang, Lisheng
Hi, I know that we need to delete/index a document in order to update any part of it, but recently we need to index a field which changes rather frequently so that each time reindexing whole document would be inpractical for performance reason. This field is a small integer so I may just trea

RE: MoreLikeThis Interface changes

2011-09-26 Thread Scott Smith
So, I thought you're response meant that I could eliminate my code: String[] fields = new String[1]; fields[0] = "EVERYTHING"; // use the single "big" field in the index mlt.setFieldNames(fields); But, if I comment out that code, my unit test fails. If I include

Re: MoreLikeThis Interface changes

2011-09-26 Thread Robert Muir
On Mon, Sep 26, 2011 at 2:06 PM, Scott Smith wrote: > "is" is the input stream.  Did I miss something in your response? > Yes, this is totally unrelated to fields[]. it has to do with which fieldname is passed to the analyzer to analyze the reader into tokens (and there can be only one for thi

RE: MoreLikeThis Interface changes

2011-09-26 Thread Scott Smith
OK. Thanks -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] Sent: Monday, September 26, 2011 12:15 PM To: java-user@lucene.apache.org Subject: Re: MoreLikeThis Interface changes On Mon, Sep 26, 2011 at 2:06 PM, Scott Smith wrote: > "is" is the input stream.  Did I miss s

Re: LuceneTaxonomyWriter unexpected shutdown

2011-09-26 Thread Shai Erera
Were there any errors / exceptions / interesting log records? Shai On Mon, Sep 26, 2011 at 7:49 PM, Mihai Caraman wrote: > Something strange happened, with no error what-so-ever. > > Ran a taxwriter in parallel with a IndexWriter, but because the indexReader > was NearRealTime, i reopened taxwri