Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <4458D5C3.1040503@apache.org>
Date: Wed, 03 May 2006 09:09:39 -0700
From: Doug Cutting <cutting@apache.org>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
MIME-Version: 1.0
To: java-dev@lucene.apache.org
Subject: Re: Control over Lucene Index
References: <44587B04.7070307@cis.strath.ac.uk>
In-Reply-To: <44587B04.7070307@cis.strath.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

You could implement the IndexReader API, then use IndexMerger to write 
this in Lucene's format.

Doug

Ralf Bierig wrote:
> 
> Hi,
> 
> in the context of a distributed information retrieval project, we would 
> like to use Lucene for its indexing capabilities but not for retrieval. 
> In particular, we would like to populate a Lucene index with the tokens 
> and statistics already computed by an external indexer, thereby 
> bypassing the document-based parsing, analysis, and ingestion into the 
> index which characterises Lucene's standard workflow. Is this possible? 
> That is, is it possible to feed precomputed statistics into a Lucene's 
> index? And is it possible to have control on what statistics are 
> associated with each document (as we will not use Lucene for retrieval 
> we are not interested in complying with the statistics it needs to 
> perform a search).
> 
> Any help greatly appreciated, many thanks.
> 
> Cheers,
> 
> 
> ---------------------------------------------------------------------
> 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