Kristian Ottosen writes:
>
> It seems to work now - but I would still love to see a good explanation.
>
How was your java application started? (sorry I you already explained,
I didn't keep the thread and the mailing list archive seems to be out
of order)
I remember strange problems (with mkdir
Hello,
A9 (Amazon's subsidiary) is looking for people, and since they are in
the information/search business people on [EMAIL PROTECTED] may be
interested in this, even though it's not Lucene-specific.
Here is an example job description:
Senior Manager and Technical Team Leader Search Infrastr
This question is very similar to a recent/current thread sith the subject
"How to include a multi-word synonym to a word when indexing?" ...
http://www.mail-archive.com/java-user@lucene.apache.org/msg00546.html
...As Erik points out in that thread, when dealing with a dictionary of
"singleword"
I am writing a document management system for my company, and many of
our feature names are in Hungarian notation (PowerQuery,
TransactionManager, etc.). This can make it hard to find some things
with a default analyzer.
I'd like to be able to index text like "Use PowerQuery for advanced
searches"
It seems like different search methods treat zero scoring docs a
little differently. Is this OK?
Some search methods on IndexSearcher check for score > 0.0f :
scorer.score(new HitCollector() {
public final void collect(int doc, float score) {
if (score > 0.0f &&
Great! Thanks for looking at it and thanks for the work around.
On Apr 12, 2005, at 1:50 PM, Yonik Seeley wrote:
A workaround until this problem is fixed in Lucene would be to add an
indexed sentinel field to a single doc in the collection that will be
larger (after) all other fields that you may
A workaround until this problem is fixed in Lucene would be to add an
indexed sentinel field to a single doc in the collection that will be
larger (after) all other fields that you may try a sort on.
Example:
String sentinel = new String(new char[]{0x});
doc.add(Field.
> Any fieldName that starts with "i" or
> below (including capitals) works. Can anyone think of what could
> possibly be going on here?
Looks like you uncovered an obscure sorting bug.
The reason that fields >= "j" fail is that your last indexed field
(and hence the last indexed term) starts w
On Apr 12, 2005, at 8:38 AM, Erik Hatcher wrote:
Could you give us a self-contained test case that reproduces this
issue?
Erik
Here is a small program that will manifest the error. Hopefully
someone can explain the problem. It happens with Lucene 1.4.2 and
1.4.3.
file: SortProblem
Hi,
Thank you for the comments and hints.
It seems like we finally solved this problem - but unfortunately without
being able to pinpoint the exact cause.
Our application did in fact follow all the Lucene concurrency rules. I
checked, double checked, bought "Lucene in Action" (that I highly rec
What drawbacks are there from replacing multiple words with its
corresponding acryonym/alias during analysis?
- Wildcard search: [cyber] [ca*] would not match [cybercafe]
- Fuzzy search: [cyber] [cage~] would not match [cybercafe]
Peter
_
Hello!
Do You mean:
I must compile the latest classes of
/lucene/java/trunk/src/java/org/apache/lucene/index (Rev.159229)
and
/lucene/java/trunk/src/java/org/apache/lucene/document (Rev.150682)
and actualize my actual version of Lucene?
Thank You for your help!!
Patricio
-Ursprünglich
Could you give us a self-contained test case that reproduces this issue?
Erik
On Apr 12, 2005, at 9:19 AM, Bill Tschumy wrote:
This problem is seeming more and more strange. It now looks like if
the fieldName I'm sorting on starts is ASCII "j" or above, the
RuntimeException is thrown.
On Apr 12, 2005, at 1:42 AM, Chris Hostetter wrote:
: You'll need some kind of lookup to know how to split a token like
: "cybercafe" into two words - once you've done that it will be easy to
: set the position increment of them to zero so that they overlay the
: original term.
but how would you se
This problem is seeming more and more strange. It now looks like if
the fieldName I'm sorting on starts is ASCII "j" or above, the
RuntimeException is thrown. Any fieldName that starts with "i" or
below (including capitals) works. Can anyone think of what could
possibly be going on here?
Good point on phrase/span queries, Hostetter.
:Assuming you have the following "phrase synonym" (and code that
:that can find them during Analysis)...
:
: [CyberCafe] => [Cyber] [Cafe]
...
: the only thing that's ever occured to me is to set the position incriment
: of all the words to "0" (but th
Maybe you can use PerFieldAnalyzerWrapper.
(I never used this)
Ernesto.
Eric Chow escribió:
But how about one document contains more than two different languages ??
Eric
On Apr 12, 2005 12:13 AM, Andy Roberts <[EMAIL PROTECTED]> wrote:
On Monday 11 Apr 2005 14:55, Mike Baranczak wrote:
Your
17 matches
Mail list logo
