: Now my concern is: the more projects I add the more different fields
: would come into play. I would not recreate the index from scratch as I'm
: doing right now but I would only remove all documents with e.g. key
: "project1" and add the new documents completely but not touching other
: project
On Samstag 25 Februar 2006 14:20, Eric Jain wrote:
> After upgrading to Lucene 1.9, an index that used to take about 9h to
> build now requires 13h. Any one else notice a decrease in performance?
A fix has now been committed to trunk in SVN, it should be part of the next
1.9 release.
Regards
D
On Feb 26, 2006, at 5:38 AM, Samuru Jackson wrote:
Hi to all!
I added some documents to my index repository this way:
Document document = new Document();
document.add(Field.Keyword("id", id));
document.add(Field.Keyword("type", type));
document.add(Field.Text("content", content));
Is it pos
Hi to all!
I added some documents to my index repository this way:
Document document = new Document();
document.add(Field.Keyword("id", id));
document.add(Field.Keyword("type", type));
document.add(Field.Text("content", content));
Is it possible to search only within a specific Field.Keyword? F
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
1) Many different fields because of different projects?
I'm accessing Lucenes index on a remote server through XML-RPC and I'ld
like to use one index for completely independent search projects. The
number of query requests is not that high (just
