This is what I did and it works fine. My untokenized fields where named:
"__AMSUNTOK__" + fieldName.
Where fieldName was the name of the tokenized field.
Bob Hastings
Ancept Inc.
Mark Miller <[EMAIL PROTECTED]>
08/05/2008 02:38 PM
Please respond to
java-user@lucene.apache.org
To
java-use
Thanks Eric,
I did find the problem using Luke, I see that all of the documents have
the same category field, so I must not be adding the field correctly when
I index them.
Bob
Bob
"Erick Erickson" <[EMAIL PROTECTED]>
06/27/2008 01:58 PM
Please respond to
java-user@lucene.apache.org
To
Actually, I do a global search and the order comes out: 1, 2, 8, 3, 5, 6,
7,8, 4, 9. I'm having trouble finding in the code where the sort actually
gets applied. Can you help me out there?
Bob
"Erick Erickson" <[EMAIL PROTECTED]>
06/27/2008 12:19 PM
Please respond to
java-user@lucene.apac
I just implemented a sorting feature on our application where the user can
change the sort on a query and reexecute the search. It works fine on
text fields where most of the documents have different field values.
However, on fields that are categories, that is, there are only four
distinct va
We are using Aspose: www.aspose.com. We are still in pre-release, it
works fine for all of the MS products. It's commercial, but is a good
deal as long as you don't have too many developers working on it, since
the licensing is per seat. We had a little trouble with thier PDF
product. The o
Using Lucene 2.3.0 I'm seeing an ArrayIndexOutOfBoundsException: 0 at
line 291 of MultiPhraseQuery.
A test should be added for (terms.length == 0).
I'm checking to see why the terms array is 0.
Bob Hastings
No noticeable performance hit, searches are not a bottleneck in our
system. We don't have disk redundancy.
Dragon Fly <[EMAIL PROTECTED]>
03/19/2008 11:47 AM
Please respond to
java-user@lucene.apache.org
To
cc
Subject
RE: Lucene on a cluster environment
Hi Robert,
Did you run into
We went through this a couple of years ago. I couldn't find the thread in
the archive but the jist of it is as follows:
1. We have a singleton thread that does all of the writing. new
Documents and deletions are queued to the writer via a database table.
2. Since searchers are "point in time
We have the same situation and use an atomic counter. Basically, we have
a SearcherHolder class and a SearcherManager class. The SearcherHolder
holds the searcher and the number of threads referencing the searcher.
When the thread that writes to the index closes the index, it sends an
event
Has anyone contributed an IndexDeletionPolicy that has been tested on an
NFS system?
Bob Hastings
Ancept Inc.
10 matches
Mail list logo
