Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Subject: Re: Numerical ids for terms?
From: Toke Eskildsen <te@statsbiblioteket.dk>
Reply-To: te@statsbiblioteket.dk
To: "dev@lucene.apache.org" <dev@lucene.apache.org>
In-Reply-To: <4DA41E2F.1020408@arbylon.net>
References: <4DA41E2F.1020408@arbylon.net>
Content-Type: text/plain; charset="UTF-8"
Organization: State and University Library, Denmark
Date: Wed, 13 Apr 2011 15:42:31 +0200
Message-ID: <1302702151.10761.14.camel@te-prime>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2011-04-12 at 11:41 +0200, Gregor Heinrich wrote:
> Hi -- has there been any effort to create a numerical representation of Lucene 
> indices. That is, to use the Lucene Directory backend as a large term-document 
> matrix at index level. As this would require bijective mapping between terms 
> (per-field, as customary in Lucene) and a numerical index (integer, monotonous 
> from 0 to numTerms()-1), I guess this requires some some special modifications 
> to the Lucene core.

Maybe you're thinking about something like TermsEnum?
https://hudson.apache.org/hudson/job/Lucene-trunk/javadoc/all/org/apache/lucene/index/TermsEnum.html
It provides ordinal-access to terms, represented with longs. In order to
make the access at index-level rather than segment-level you will have
to perform a merge of the ordinals from the different segments.

Unfortunately it is optional whether the codec supports ordinal-based
terms access and the default codec does not, so you will have to
explicitly select a codec when you build your index.


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