Re: Distributed Indexes.

Are you looking for something a la http://wiki.apache.org/solr/CollectionDistribution ? Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> To: java-user@lucene.apache.org Sent: Monday, October 29, 2007 4:05:

Re: Threading Indexing Processes : Can we write concurrently to Index?

30 okt 2007 kl. 05.08 skrev Michael Prichard: If I multithread an indexing process can two or more processes write to the same index? Multiple threads can add documents to the same writer. Multiple threads can usually not write using each a writer. -- karl -

Threading Indexing Processes : Can we write concurrently to Index?

The subject pretty much describes the issue. If I multithread an indexing process can two or more processes write to the same index? My knowledge of Lucene says no but I am hoping that I am missing something. Also, what is a good solution? Thanks. Michael --

Distributed Indexes.

HI Folks, We are planning on distributing our index data bases. Has any one got any recommendations, code samples to how this can be acheived. Also please provide any performance hits or bottle necks. Thanks Much _Durga -

Re: Create and populate a field when indexing

When you are indexing the file and adding the Document, you will need to parse out your filename per your regular expression, and then create the appropriate field: Document doc = new Document() String cat = getCategoryFromFileName(inputFileName) doc.add(new Field("category", cat, ...) //do t

Create and populate a field when indexing

I've been using the Lucene demo from http://lucene.apache.org/java/2_1_0/demo.html I have a set of documents with filenames that give a good indication of content. A filename of 12 digits (I think this is [0-9]{12} as a regular expression) with the extension html is a troubleshooting guide, the

Re: Search performance using BooleanQueries in BooleanQueries

On Friday 26 October 2007 09:36:58 Ard Schrijvers wrote: > Hello, > > I am seeing that a query with boolean queries in boolean queries takes > much longer than just a single boolean query when the number of hits if > fairly large. For example > > +prop1:a +prop2:b +prop3:c +prop4:d +prop5:e > > is

Problem with ConstantScoreRangeQuery

I am programatically creating a query as follows. BooleanQuery query = new BooleanQuery(); ConstantScoreRangeQuery range = new ConstantScoreRangeQuery ("creationDate", "19500101", "20071029", false, false); query.add(range, Occur.MUST); I am

Re: TermDocs.skipTo

Mike Streeton wrote: > e.g. Iterating using TermDocs.next() and TermDocs.doc() 1,50,1,2 but > suing TermDocs.skipTo(51) returns false indicating that no doc id > 50 exists. Hi Mike, I quickly tried to reproduce this (with the same docids), but for me skipTo() works fine, i. e. td.skipTo(

TermDocs.skipTo

Are there any issues surrounding TermDocs.skipTo(). I have a index that works okay if I use TermDocs.next() to find next doc id, but using skipTo to go to the one after a point can miss sometimes. e.g. Iterating using TermDocs.next() and TermDocs.doc() 1,50,1,2 but suing TermDocs.skipTo