Re: WildCard search replacement

Glad to help you. Aalap Parikh wrote: Thanks very much. Volodymyr, your trick about wildcard search replacement has helped me a lot. Great idea!!! Thanks a lot again. --- Volodymyr Bychkoviak <[EMAIL PROTECTED]> wrote: Hi. Aalap Parikh wrote: Hi, The idea about begin marker sounds good. And

Re: WildCard search replacement

Thanks very much. Volodymyr, your trick about wildcard search replacement has helped me a lot. Great idea!!! Thanks a lot again. --- Volodymyr Bychkoviak <[EMAIL PROTECTED]> wrote: > Hi. > > Aalap Parikh wrote: > > >Hi, > > > >The idea about begin marker sounds good. And the > >prefix could be

Re: Implementation of a ScoreObject ?

Robichaud, Jean-Philippe wrote: Probably the simplest/ideal schema of the ScoreObject would be something like a hashtable with Term being the keys and a TermScoreObject the value. The TermScoreObject would be filled at search time (if asked) and would contain all values used in the calculation of t

Re: Indexing of virtual "made up" documents

Morus Walter wrote: Alternatively it should be able to write a query that does such a scoring directly (without the document start anchor) by the same means proximity query uses. Proximity query uses positional information so it should be possible to use that information for scoring based on docum

Implementation of a ScoreObject ?

Hi Everyone, Lucene is incredible for a lot of reasons. I've been using it for the past months and it served me quite well. I'm using the subversion snapshots, which I update every now and then. Almost every functionality I need is already present and well implemented, but sadly

RE: FilteredQuery and Boolean AND

Chris, Sorry for the delay... I added a test case like this: (FilteredQuery1 AND FilteredQuery2) OR TermQuery See my email below for details. Although this doesn't really add anything new to the problem, it just illustrates that applying a chained filter at search time won't always work. It w

Re: Question about Boosting Fields in a Query

On Apr 27, 2005, at 11:02 AM, Sven wrote: Hi folks, I have a question about boosting fields in a Query. Suppose we have documents like this in the index: fieldA:String fieldB:String fieldC:Date fieldD:Number And the query is like that: fieldA: wordA1 wordA2 wordA3 wordA4 fieldB: wordB1 wordB2 wordB

Re: Question about Boosting Fields in a Query

Hi Sven, http://www.lucenebook.com/search?query=search+boost+field (hm, I was hoping to find something better) You can use setBoost at search time: Query class has setBoost(float) method, which you can use if you construct queries in the code, and QueryParser supports ^float syntax, which puts th

Question about Boosting Fields in a Query

Hi folks, I have a question about boosting fields in a Query. Suppose we have documents like this in the index: fieldA:String fieldB:String fieldC:Date fieldD:Number And the query is like that: fieldA: wordA1 wordA2 wordA3 wordA4 fieldB: wordB1 wordB2 wordB3 wordB4 fieldC:[date1 to da

Re[2]: multi word synonym (was Hungarian notation analyzer and phrase queries)

Hello, What about the solution to index every multi-word synonym as a single token ? Example : Phrase to index : "i love jsp and tomcat" Synonyms: "jsp" = "java server pages" = "javaserver pages" Tokens : i love jsp and tomcat java server pag