Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <89BB17546E0E474D96B24BFDE996C050@VEGA>
References: <85d3c3b60906091932i591ef6f4gcc950586b15d4506@mail.gmail.com>
	 <85d3c3b60906101058w1f6b5fc5re5a2911cdc8053c1@mail.gmail.com>
	 <444929E412B144B6AB5F6CF3CC919D36@VEGA>
	 <9ac0c6aa0906101145p3450edf6v2a9378c8925412b8@mail.gmail.com>
	 <D2F38D08D3F848768F7DA2B14B8120A0@VEGA>
	 <c68e39170906101219j73d05af3gcb42b99bca356d82@mail.gmail.com>
	 <9ac0c6aa0906101243o1f018b84h929e357e0fa8f88e@mail.gmail.com>
	 <c68e39170906101310m1afba606kf64e865288dff55e@mail.gmail.com>
	 <50E85C764334475D8E8C8597EA2EC5EB@VEGA>
	 <89BB17546E0E474D96B24BFDE996C050@VEGA>
Date: Wed, 10 Jun 2009 17:32:27 -0400
Message-ID: <9ac0c6aa0906101432w7a836a1av329a9bfd745523de@mail.gmail.com>
Subject: Re: Payloads and TrieRangeQuery
From: Michael McCandless <lucene@mikemccandless.com>
To: java-dev@lucene.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I think we'd need richer communication between MTQ and its subclasses,
so that eg your enum would return a Query instead of a Term?

Then you'd either return a TermQuery, or, a BooleanQuery that's
filtering the TermQuery?

But yes, doing after 3.0 seems good!

Mike

On Wed, Jun 10, 2009 at 5:26 PM, Uwe Schindler<uwe@thetaphi.de> wrote:
>> I would like to go forward with moving the classes into the right packages
>> and optimize the way, how queries and analyzers are created (only one
>> class
>> for each). The idea from LUCENE-1673 to use static factories to create
>> these
>> classes for the different data types seems to be more elegant and simplier
>> to maintain than the current way (having a class for each bit size).
>>
>> So I think I will start with 1673 and try to present something useable,
>> soon
>> (but without payloads, so the payload/position-bits setting is "0").
>
> Another question not so simple to answer: When embedding these TermPositions
> into the whole process, how would this work with MultiTermQuery? The current
> algorithm is simple: The TrieRangeTermEnum simply enumerates the possible
> terms from the index and MTQ creates the BitSet or a BooleanQuery of
> TermQueries. How to do this with positions? In both cases there need
> specialities (the TermEnum must return that the actual term is a
> payload/position one and must filter using TermPositions). For the filter
> its then easy, the TermQueries added to BooleanQuery in the other case must
> also use the payloads. Questions & more questions.
>
> I tend to release TrieRange with 2.9 without Positions/Payloads.
>
> Uwe
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org