I'd think about the filter option first, see below
On 6/5/07, lucene user <[EMAIL PROTECTED]> wrote:
We have a large and growing number of articles (< 60k but growing) and we
want to divide
articles from some sources into groups so that we can do queries against
just members of
one or two grou
Hi Hilton,
Hilton Campbell wrote:
> Hello all,
>
> In my application I want to perform a search over all the documents
> that are NOT in a certain subset, and I'm not sure how I should do
> it.
>
> Specifically, the application performs a search and the top N results
> are shown to the user. The
We have a large and growing number of articles (< 60k but growing) and we
want to divide
articles from some sources into groups so that we can do queries against
just members of
one or two groups and not find articles from publications that are outside
these publication
groups.
We would like to b
Hello all,
In my application I want to perform a search over all the documents that are
NOT in a certain subset, and I'm not sure how I should do it.
Specifically, the application performs a search and the top N results are
shown to the user. The user may then opt to see the next top N results.
Hi Divya,
The Lucene library itself provides no support for "backup".
You might be interested in the Solr project[1], which extends Lucene,
and which automates index replication. From the Solr Introduction /
Features page[2]:
Replication
* Efficient distribution of index parts that have
Hello, Any advice on this would be of great help.
Thanks
-Original Message-
From: Rajendranath, Divya
Sent: Tuesday, June 05, 2007 10:59 AM
To: java-user@lucene.apache.org
Subject: Maintain a backup index
We want to maintain a backup of our production index directory. We are
using Luce
Hi
you can get them from searcher, if documents in your index are the same
Enumeration fields = searcher.doc(0).fields();
On 6/5/07, Stadler Hans-Christian <[EMAIL PROTECTED]> wrote:
Hi,
how would I efficently retrieve the names of all possible fields present
in an index?
One way would be
Would IndexReader.getFieldNames work?
Erick
On 6/5/07, Stadler Hans-Christian <[EMAIL PROTECTED]> wrote:
Hi,
how would I efficently retrieve the names of all possible fields present
in an index?
One way would be to iterate over all terms and extract the field names,
but it doesn't
look like
Hi,
how would I efficently retrieve the names of all possible fields present in an
index?
One way would be to iterate over all terms and extract the field names, but it
doesn't
look like this method is efficient for large indices.
Murphy for president!
HC
-
On 6/5/07, Michael Böckling <[EMAIL PROTECTED]> wrote:
In the docs it says that I should cache the IndexSearcher for best
performance, and not build a new one for each query.
The problem is that when I want to switch to a new index, I would have to
synchronize my search() method while my update
Hi folks!
In the docs it says that I should cache the IndexSearcher for best
performance, and not build a new one for each query.
The problem is that when I want to switch to a new index, I would have to
synchronize my search() method while my update check runs (which is also
synchronized), so se
11 matches
Mail list logo