: When I create a TermQuery, add it as a SHOULD clause to a BooleanQuery, and
: boost that BooleanQuery, the boost shows up when I run
: IndexSearcher.explain(). However, when I add a second TermQuery as a SHOULD
: clause to that same BooleanQuery, and still boost the BooleanQuery, the
: boost is
Op Saturday 30 August 2008 18:22:50 schreef Matt Ronge:
> On Aug 30, 2008, at 6:13 AM, Paul Elschot wrote:
> > Op Saturday 30 August 2008 03:34:01 schreef Matt Ronge:
> >> Hi all,
> >>
> >> I am working on implementing a new Query, Weight and Scorer that
> >> is expensive to run. I'd like to limit
Op Saturday 30 August 2008 18:19:09 schreef Matt Ronge:
> On Aug 30, 2008, at 4:43 AM, Karl Wettin wrote:
> > Can you tell us a bit more about what you custom query does?
> > Perhaps you can build the "candidate filter" and reuse it over and
> > over again?
>
> I cannot reuse it. The candidate filt
Hi guys,
Fairly new to Lucene, and just finished reading Lucene in Action.
My problem is the following I need to index the documents that only contains
the following pattern(s) in a mass of documents:
<#1> <#2>
is a fixed list of words
<#x> are small numbers <100
My idea is to simply build a
Matt Ronge wrote:
Hi all,
I am working on implementing a new Query, Weight and Scorer that is
expensive to run. I'd like to limit the number of documents I run this
query on by first building a candidate set of documents with a boolean
query. Once I have that candidate set, I was hoping I cou
Hi guys,
Fairly new to Lucene, and just finished reading Lucene in Action.
My problem is the following I need to index the documents that only contains
the following pattern(s) in a mass of documents:
<#1> <#2>
is a fixed list of words
<#x> are small numbers <100
My idea is to simply build a
On Aug 30, 2008, at 4:43 AM, Karl Wettin wrote:
Can you tell us a bit more about what you custom query does? Perhaps
you can build the "candidate filter" and reuse it over and over again?
I cannot reuse it. The candidate filter would be constructed by first
running a boolean query with a n
On Aug 30, 2008, at 6:13 AM, Paul Elschot wrote:
Op Saturday 30 August 2008 03:34:01 schreef Matt Ronge:
Hi all,
I am working on implementing a new Query, Weight and Scorer that is
expensive to run. I'd like to limit the number of documents I run
this query on by first building a candidate se
Op Saturday 30 August 2008 03:34:01 schreef Matt Ronge:
> Hi all,
>
> I am working on implementing a new Query, Weight and Scorer that is
> expensive to run. I'd like to limit the number of documents I run
> this query on by first building a candidate set of documents with a
> boolean query. Once I
30 aug 2008 kl. 09.42 skrev Andre Rubin:
I have 2 indexes. Both have an ID field and one or more String
fields... I
want to merge these indexes by merging the documents on each index
that
match their IDs.
Is there a way to do that in an efficient way, like not having to
manually
travers
MoreLikeThis needs to find the terms in your doc. It tries to do this by using
TermFreqVectors which are stored in the index if you choose to add them at
index-time. If you haven't done this then it will fall back to reanalysing the
content of the document usings an analyser (despite what the j
Can you tell us a bit more about what you custom query does? Perhaps
you can build the "candidate filter" and reuse it over and over again?
karl
30 aug 2008 kl. 03.34 skrev Matt Ronge:
Hi all,
I am working on implementing a new Query, Weight and Scorer that is
expensive to run. I'
Hey all
I have 2 indexes. Both have an ID field and one or more String fields... I
want to merge these indexes by merging the documents on each index that
match their IDs.
For exmaple:
Index 1:
Doc1:
id: 1234 (*)
text:bla bla
text:abcd
Index2:
DocA:
id:1234 (*)
text:xyz
(*) ID's match
So I w
13 matches
Mail list logo
