Hello,
I am trying to compile the analyzers from the Lucene sandbox contributions. Many of
them seem to import org.apache.lucene.analysis.WordlistLoader which is not currently
in my classpath.
Does anyone know where I can find this class? It does not appear to be in Lucene 1.4,
so I am
That is interesting.
I went to lookup the cases for this (on Google).
Here are my 4 queries and the results:
a) of the from it
- 25,500,000 matches containing 'of' and 'the' and 'from' and 'it'
- i.e. stop list NOT used if query is only stopwords
b) of the from it
very similar.
Erik
On Aug 18, 2004, at 11:52 AM, Tate Avery wrote:
That is interesting.
I went to lookup the cases for this (on Google).
Here are my 4 queries and the results:
a) of the from it
- 25,500,000 matches containing 'of' and 'the' and 'from' and 'it'
- i.e
Well, as far as I know you can boost 3 different things:
- Field
- Document
- Query
So, I think you need to craft a solution using one of those.
Here are some possibilities for each:
1) Field
- make a keyword field which is alongside your content field
- boost your keyword
I had to do this once and I put a field called all with a value of true for every
document.
_doc.addField(Field.Keyword(all, true));
Then, if there was an empty query, I would substitute it for the query all:true.
And, of course, every doc would match this.
There might be a MUCH more
for your time,
Tate Avery
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
From: Tate Avery [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 29, 2004 1:30 PM
To: 'Lucene Users List'
Cc: [EMAIL PROTECTED]
Subject: RE: Understanding Boolean Queries
Thank you for the response.
I am not using the QueryParser directly... it was just part of my overall
understanding
Hello,
I am using Lucene 1.3 and I ran into the following exception:
java.lang.IndexOutOfBoundsException: More than 32 required/prohibited
clauses in query.
at org.apache.lucene.search.BooleanScorer.add(BooleanScorer.java:98)
Is there any easy way to fix/adjust this (like the
Or if I overlooked some previous post or thread that covers this please help
me track it down.
Thank you,
Tate
-Original Message-
From: Tate Avery [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 27, 2004 10:20 AM
To: [EMAIL PROTECTED]
Subject: BooleanScorer - 32 required/prohibited
Also...
http://jazzy.sourceforge.net/
-Original Message-
From: Felix Huber [mailto:[EMAIL PROTECTED]
Sent: Friday, April 16, 2004 1:17 PM
To: Lucene Users List
Subject: Re: Software for suggesting alternative words or sentences
Check http://www.iu.hio.no/~frodes/sprell/sprell.html -
Hello,
Is there a way (direct or indirect) to support a field with numeric data?
More specifically, I would be interested in doing a range search on numeric
data and having something like:
number:[1 TO 2]
... and not have it return 11 or 103, etc. But, return 1.5, for example.
Is
Hello,
If I have, for example, 3 fields in my document (title, body, notes)... is there some
easy what to search 'all'?
Below are the only 2 ideas I currently have/use:
1) If I want to search for 'x' in all, I do something like:
title:x OR body:x OR notes:x
... but this does not
Could you put them all into a tab-delimited string and store that as a
single field, then use a TabTokenizer on the field to search?
And, if you need to, do a .split(\t) on the field value in order to break
them back up into individual categories.
-Original Message-
From: David Black
Try:
String larequet = query.toString(default field name here);
Example:
String larequet = query.toString(texte);
That should give string version of query.
-Original Message-
From: Gayo Diallo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 17, 2003 10:46 AM
To: [EMAIL
Hello,
This is the first time that I noticed this.
Is the 'powered by Lucene' a legal requirement? Or just a suggestion?
Does it apply to any system embedding Lucene (web pages, applications, etc)?
That is not covered in the Apache Software License, I believe.
Just curious...
Tate
If you buy it, apparently:
http://www.searchblox.com/buy.html
-Original Message-
From: Tun Lin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 02, 2003 10:43 AM
To: 'Lucene Users List'; [EMAIL PROTECTED]
Subject: RE: SearchBlox J2EE Search Component Version 1.1 released
Hi,
Have a look at the API
http://jakarta.apache.org/lucene/docs/api/
For example, the Hits object has a score
see: org.apache.lucene.search.Hits (score)
And the IndexReader allows you to get num docs in the index and term data, etc.
see: org.apache.lucene.index.IndexReader
Hello,
I am considering using the document id in order to implement a fast 'join' during
relational search.
My first question is: should I steer clear of this all together? And why? If not, I
need to know which Lucene operations can cause document ids to change.
I am assuming that the
Categorization typically assigns documents to a node in a pre-defined taxonomy.
For clustering, however, the categorization 'structure' is emergent... i.e. the
clusters (which are analogous to taxonomy nodes) are created dynamically based on the
content of the documents at hand.
-Original
Hello,
I want to perform a 'relational search' meanining that I want to search 2 indexes and
perform an intersection between the 2. It would be very much like a table join in an
SQL statement in terms of overall result.
So, I might have an index of documents of type A that would allow me to
Below are some posts from Doug (circa 2001) that I found very helpful with regard to
understanding Lucene scalability. I am assuming that they are still generally
applicable. You might also find them useful.
Tate
---
Performance for
To ensure I understand...
If you have:
1) A B C
2) B C
3) B C D
4) C
You want B C to match #2 only
But, C to match #1, #2, #3, and #4
If so, you can have a tokenized field and an untokenized one...
Use the untokenized for matching 'exact' strings
Use the tokenized for finding a single
22 matches
Mail list logo
