Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of rene.a.hackl@gmx.de
 designates 213.165.64.20 as permitted sender)
Message-ID: <4B9EA211.4060206@gmx.de>
Date: Mon, 15 Mar 2010 22:09:37 +0100
From: Rene Hackl-Sommer <rene.a.hackl@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de;
 rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: java-user@lucene.apache.org
Subject: Re: Increase number of available positions?
References: <4B9DF7DE.9070209@gmx.de>
	 <359a92831003150536o5cfd573eq7523234346a5ab38@mail.gmail.com>
	 <4B9E3D57.6050402@gmx.de>
 <359a92831003150921g3db5cadbo803d36c658b11b81@mail.gmail.com>
In-Reply-To: <359a92831003150921g3db5cadbo803d36c658b11b81@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Erick,
> What about indexing
> the triplets with a small increment gap between? That is:
> ...
> gets indexed as:
>
> level1-1/level2-1/level3-1  +gap 100
> level1-1/level2-1/level3-2  +gap 100
> level1-1/level2-2/level3-3  +gap 100
> level1-1/level2-2/level3-4
>    

If I understand this correctly, the field would look like 
"level1-1/level2-1/level3-1 Term1 Term2 level1-1/level2-1/level3-2 Term3 
Term4 "?

I think, the problem here is the same like in the Payloads approach I 
wrote of in my response to Steve's mail. We cannot test for equality at 
search time (please correct me if we actually can do this). So if we have

level1-1/level2-1/level3-1
...
level1-1/level2-1/level3-244
level1-1/level2-2/level3-1
level1-1/level2-2/level3-105

and I search for T1 and T2 on level3, but want them to be in the same 
level2, this cannot be done satisfactorily.

> Or you could think about *documents* being your level1, that is each
> document has one and only one level1 element but many documents
> may have the same level1 token. Combining this with your increment
> gap notion for level2-3 might work for you.
>    

I was thinking about this, yet the trouble is that the issue at hand is 
just one field in an already not quite trivial scenario involving 200+ 
fields. If I add say 50 level1-documents per real document, I would 
still need to be able to relate these level1-documents to the real 
documents to which they belong, and, during retrieval, there are use 
cases where I need to look into each of the level1-documents to see if 
they fulfill certain criteria and then, in a further step, ascertain 
whether I can gather the needed level1-documents to fulfill the query on 
a "MyField"-Level (not existant here per se). I feel this might get 
somewhat unwieldy.

> You might also search the list for "Heirarchal" or "tree" indexing,
> this is a variant of such I think.
>    

Thank you, I'll look into this.

Cheers
Rene

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