Well there really is no concrete plan/timeline at this point --
that is the nature of open source.
But there are some issues in flight that take us on the first few
steps towards flexible indexing.
I think LUCENE-1301 (which I'm working on and should be done soon, in
2.4 I think) i
Hi Michael:
What is the plan/timeline for supporting flexible indexing?
Thanks
-John
On Wed, Jun 25, 2008 at 3:40 AM, Michael McCandless <
[EMAIL PROTECTED]> wrote:
>
> John Wang wrote:
>
> The problem I am having is stated below, I don't know how to add the
>> minDoc and maxDoc value
I am not sure, BooleanQuery takes something that can score, e.g. being a
Clause or a Query, the contract requires some sort of scoring functionality.
We use DocIdSetQuery for some of the scoring capabilities such as constant
score (with boosting), age decay, and using the new scoring api in 2.3.
Ma
Op Wednesday 25 June 2008 18:45:16 schreef John Wang:
> Hi Paul:
> Regarding to your comment on adding required/prohibited to
> BooleanQuery:
>
> Based on the new api on DocIdSet and DocIdSetIterator
> abstractions, we also developed decorators such as
> AndDocIdSet,OrDocIdSet and NotDocIdS
Hi Paul:
Regarding to your comment on adding required/prohibited to BooleanQuery:
Based on the new api on DocIdSet and DocIdSetIterator abstractions, we
also developed decorators such as AndDocIdSet,OrDocIdSet and NotDocIdSet,
furthermore a DocIdSetQuery class that honors the Query api con
Op Wednesday 25 June 2008 17:05:17 schreef John Wang:
> Thanks Paul and Mike for the feedback.
> Paul, for us, sparsity of the docIds determine which data structure
> to use. Where cardinality gives some of that, min/max docId would
> also help, example:
>
> say maxdoc=100, cardinality = 7, doc
Thanks Paul and Mike for the feedback.
Paul, for us, sparsity of the docIds determine which data structure to use.
Where cardinality gives some of that, min/max docId would also help,
example:
say maxdoc=100, cardinality = 7, docids: {0,1,...6} or
{3,4...9}, using arrayDocIdSet wou
John Wang wrote:
The problem I am having is stated below, I don't know how to
add the minDoc and maxDoc values to the index while keeping backward
compatibility.
Unfortunately, TermInfo file format just isn't extensible at the
moment, so I think for now you'll have to break backward
Op Wednesday 25 June 2008 07:03:59 schreef John Wang:
> Hi guys:
> Perhaps I should have posted this to this list in the first
> place.
>
> I am trying to work on a patch to for each term, expose minDoc
> and maxDoc. This value can be retrieve while constructing the
> TermInfo.
>
> Know
eatly appreciated.
Thanks
-John
-- Forwarded message --
From: John Wang <[EMAIL PROTECTED]>
Date: Tue, Jun 24, 2008 at 11:59 AM
Subject: changing index format
To: [EMAIL PROTECTED]
Hi:
I am trying to add couple more values to the TermInfo file and want to
keep the ind
10 matches
Mail list logo
