Just a user and mailing list lurker - but I say go for it - I think even
WebSphere is running under 1.4 these days.
If people complain, tell them that since they don't see the need to upgrade
their JVM, they also shouldn't need to upgrade Lucene :)
Dan
-Original Message-
From: Erik Hat
I don't believe that Lucene is read locked for search. It is only for initializing
the IndexReader's. So, if each of your JVM's create and keep an IndexReader open,
each of your JVM's should be able to search on your single disk concurrently.
Just don't create a new IndexReader every time yo
It would be nice if these items in the sandbox would have a pre-compiled copy sitting
somewhere easy to download. Highlighting seems to be a fairly common question on
these lists from beginners, and having to go to cvs, check them out, and then compile
them (when many don't have ant scripts) is
Heres my quasi code (I just copied and pasted out the important pieces).
final ArrayList tempHits = new ArrayList(index.maxDoc() / 4);
searcher.search(query, filter, new HitCollector()
{
public vo
Maybe you should add another page (or section on the page) that is for people to list
the names of their companies or products that are using lucene (with a brief
description of what for), as the current page only shows that Lucene is used for
indexing web pages, or web viewable things.
I know
I've noticed an oddity in scoring
If I do my search like this:
searcher.search(query, filter, new HitCollector()
{
public void collect(int doc, float score)
{
tempHits.add(new LuceneHits(doc, score));
}
});
I get different scores for the resulting doc
I'm not a voter, but as a user, I would prefer to see the lucene jar with the core
classes stay as small as possible, and the analyzers be included in a second jar file
in the distribution.
So,
1 download
separate jar files.
-
I would have to agree with Peter on this issue. Also, Doug's solution makes a lot of
sense to me. If I had the right to vote, that would be the solution I would choose.
*
Daniel C. Armbrust
Medical Informatics Research
Information Services
Mayo Clinic Rochester
I think that was what started the discussion... panhenryk posted it to the mailing
list on Monday (subject - wildcard preceding term solution), and then (I'm assuming
this is the same person but it may not be) [EMAIL PROTECTED] submitted this bug
report about it with his changes attached. Both
I think that the only difference we have is that you see the Query Parser as a
convenience for the app users, while I see it as a convenience to the app users and
the app developers. Its probably a good thing to ship lucene with the query parser
that doesn't allow you to do the search that mak
I don't know much about the implementation details of the Query Parser.
>From previous conversations on the list, I get the idea that allowing wildcards as
>the first letter of a search introduces a large performance hit.
But I also think that this feature should be implemented by a search engi
This is part of the reason I keep poking the list for better number support
(and still haven't heard a "peep" as Phil would say about them, so I am
guessing that one or the other or both of
A: It would take to much redesign to make lucene handle numbers better
B: No one else has a need for inde
Can numeric support be added to the todo list? I realize that James Ricci
and I are the only two that have requested it recently and maybe its an
unreasonable request for lucene, due to its design and the amount of work it
would take to implement it - which I'm willing to live with - but I ha
Another suggestion -
Real support for indexing of numbers. Especially for filtering on them, so
that it doesn't have to be implemented in the fashion of the date filter
with bit set vectors and alphabetic numbers.
I have no idea how difficult this is to implement, but I know I would have a
use
Maybe this is being overlooked - but on the main page where it says "Lucene
v1.02 released - This release repackages Lucene as a product of the Apache
SoftwareFoundation. Download it here"
is version 1 . 0 2 (one point ZERO two)
while the current release candidate is 1.2 RC4 - (one point two
+ 1 on this Dmitry's votes.
-Original Message-
From: Dmitry Serebrennikov [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 27, 2002 12:09 PM
To: Lucene Developers List
Subject: Re: cvs commit: jakarta-lucene build.xml
As a new and cluless user of Ant, here's my vote:
+1 on not
16 matches
Mail list logo
