Ahh, interesting point, though I'm afraid it solves a different
problem than my intentions. Re-reading this, I think I've described my
problem in a very obscure way. Sorry :-/.
Basically, pretend I do a regular search for "category:fiction". After
stemming/etc, this would match any Document with
Mr Plate wrote:
This puzzle has been bugging me for a while; I'm hoping there's an
elegant way to handle it in Lucene.
DATA DESCRIPTION:
I've got an index of over 100,000 Documents. In addition to other
fields, each of these Documents has 0 or more "category" field values.
There are over
Lucene is more like an engine, while Dieselpoint is more like a car.
AFAIK, Dieselpoint is doing database search, but not using Lucene.
You are welcome to try DBSight, which crawls database in a
customizable way and uses Lucene. You can set it up quickly and see if
Lucene fit your performance and
This puzzle has been bugging me for a while; I'm hoping there's an
elegant way to handle it in Lucene.
DATA DESCRIPTION:
I've got an index of over 100,000 Documents. In addition to other
fields, each of these Documents has 0 or more "category" field
values. There are over 5,500 such catego
chandler burgess wrote:
Im using lucene1.4.3 on a XP machine with jdk1.5. Any help is appreciated.
Try typing control-break to get some stack dumps. I also recommend
building the current Lucene code from subversion and trying that. There
have been lots of improvements since 1.4.3.
It woul
There isn't much to the code. The first line of main() literally just calls
IndexReader.open() and it never gets past that line. Nothing fancy. I have
one app that built the index, and this one just searches it. Do you think it
could the fact that I optimized it?
If you really insist on seeing
Hi,
Maybe post some of the code which is giving you problems and people can view
it and try and see what's wrong.
Cheers,
MC
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hello, I have a 6GB index consisting of about 4M documents, each with 2
fields. The index built fine and then I optimized it. Whenever I try to open
the index, though, the jvm crashes saying it has run out of heap space. Even
when I increase the heap size it just runs longer and then crashes. Wi
Hi all,
Within our application it is possible for users to add reactions for
files. It is a requirement that a search returns a file if the query
matches the contents or a reaction. I think it would be best to use to
different indexes, one for the file and another one for the reactions.
Searchi
On Dec 15, 2005, at 10:34 AM, javier muguruza wrote:
thanks all,
Yes, I know + means it must be true, but the phrase goes through the
same analyzer, so stop words are removed
I made some debugging and I got this:
Query query = QueryParser.parse(searchexp, "body",
LuceneHelper.getAnalyze
thanks all,
Yes, I know + means it must be true, but the phrase goes through the
same analyzer, so stop words are removed
I made some debugging and I got this:
Query query = QueryParser.parse(searchexp, "body", LuceneHelper.getAnalyzer());
If searchexp is
((+(body:"I have")) OR (+(attachment
With the '+' prefix you are saying that both clauses must be true, so
looking for stopwords will return false since it won't find any match.
Regards,
Daniel
-javier muguruza <[EMAIL PROTECTED]> escribió: -
Para: Lucene Users List
De: javier muguruza <[EMAIL PROTECTED]>
Fecha: 15/1
Hello All,
We've been using Lucene here and like it, but we've been asked to look
into another engine also (Dieselpoint). Has anyone used both Dieselpoint and
Lucene. Any comments. We have a lot of documents (50 million+) each document
contains many small fields (maybe 100s). Important features
I will be out of the office starting 12/15/2005 and will not return until
12/21/2005.
I will respond to your message when I return.
For NXP issues, please contact Kasi Reddy/Stephen Thompson, For
Harrisdirect issues, please contact Dave Wong/Clifford Newlands
Thank you.
-
Are you using the same Analyzer for both indexing and querying (or the
same StopFilter at least)?
-Yonik
On 12/15/05, javier muguruza <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Suppose I have a query like this:
> +attachments:purpose
> that returns N hits.
> If I add another condition
> +attachments:
The latest binary "stable" release is 1.4.3. Though not officially
released, Lucene 1.9 is available from the source code repository, and,
IMHO, is more than ready for day to day use. You will need to check the
code out with subversion or cvs via the apache code repository and build it
your self.
That is certainly the behaviour I would expect. The "+" means the term or
phrase is required - you are requiring words that are not stored in your
index.
Why don't remove the "+"? Alternately you could run the search, and if no
matches are found, run it again without the second argument. I've fo
Hi,
When we do a search for
"The integration of ERP into a logistics curriculum: applying a systems"
We get an index out of bounds exception.
There is a bug within bugzilla that indicates this problem.
Bug number. 10052
However this bug states the fixes have been included within the latest
r
I will be out of the office starting 12/15/2005 and will not return until
12/21/2005.
I will respond to your message when I return.
For NXP issues, please contact Kasi Reddy/Stephen Thomson, For
Harrisdirect issues, please contact Dave Wong/Clifford Newland
Thank you.
---
Hi,
Suppose I have a query like this:
+attachments:purpose
that returns N hits.
If I add another condition
+attachments:purpose +attachments:"hello world"
I still get some hits, but if the words in the "hello world" phrase
happen to be all stop words I get 0 hits.
I can fix that by checking at
20 matches
Mail list logo
