Re: Boosting query - debuging

I looked into the output again, and saw that the explain method, explains a different result then the document i thought it did. Within the loop of the results, I replaced int docId = hits[j].doc; Document curDoc = searcher.doc(docId); with Document curDoc = searcher.doc(j); So I got the right

Re: lucene / hibernate search in cluster

Hi, There are many more alternatives available to the JMS bridge. There is also the abilty to do incremental copy of the index over a shared filesystem for instance. That being said, 5 seconds seems really short to me. I read all this in "Hibernate Search In Action" but I suppose the online mater

lucene / hibernate search in cluster

We are using hibernate search that is an abstraction on top of lucene. Has anyone used this in a clustered environment? There is built-in JMS ( master / slave ) support for this but the assumption is that the slaves get updates every 30 minutes or more from the master. Our application requires t

get term neighbours

Hello, I am post-processing a positional index -- with a field like the following: doc.add(new Field(Constants.FIELD_TEXT, txt, Store.NO, Index.ANALYZED, TermVector.WITH_POSITIONS)); At post-processing, I want to retrieve the neighbours of a given term within a given range. That is, if docum

Boosting query - debuging

Hi, I try to debug boosting query. Is there a way to see the term boost in the documents? I see them in spans in BoostingTermQuery, yet, from there I can't see which document I am in. If I want to copy some of the document in an index that saves the boosting - how can it be done? The problem I am

Re: Query scoring

Please see in a new thread - Boosting query - debuging Thanks! 2009/5/2 Chris Hostetter > > : Sorry, you can see the script below: > > uh ... ok. so now you've posted a bunch of your code, but you still > haven't addresed the root of what Erick and I were both getting at... > > : > Erick means

why setPhraseSlop() make no diffrence

I have ste the slop for my search to be some terms away for inclusion. unfortunately, the result is the same indpendent of my setPhraseSlop(int) usage. code excerpts: == QueryParser qp = new QueryParser("content", new AmharicAnalyzer()); qp.setPhraseSlop(3);