Kevin Burton writes:
>
> How much interest is there for this? I have to do this for work and
> will certainly take the extra effort into making this a standard Lucene
> feature.
>
Sounds interesting.
How would you handle deletions?
Morus
-
Claude Devarenne writes:
> Hi,
>
> I have over 60,000 documents in my index which is slightly over a 1 GB
> in size. The documents range from the late seventies up to now. I
> have indexed dates as a keyword field using a string because the dates
> are in MMDD format. When I do range que
On May 18, 2004, at 3:56 PM, Claude Devarenne wrote:
Thanks, I'll try that. It would nice too if I could extend field (it
is a final class) and create a numerical field. Is that not
desirable?
It isn't that much more effort to have something like NumberUtils
listed here:
http://wiki.apache.or
> Is there a simpler, easier way to do this?
Yes. I have started implementing a "QuickRangeQuery" class, that doesn't
have the BooleanQuery limitation, but scores every matching document as 1.0.
I will see if I can get it finished in the next 24 hours, and post back
to this thread.
=Matt
PS: I'
Hi,all,
Can we do search and update one index simultaneously?Is someone know sth
about it? I had done some experiments.Now the search will be blocked
when the index is being updated.The error in search node is like this:
caught a class java.io.IOException
with message:Stale NFS file handle
Thanks, I'll try that first and then Ype's suggestion if necessary. I
have been shying away from filters so now I have no excuse ;-)
Claude
On May 18, 2004, at 1:35 PM, Andy Goodell wrote:
In our application we had a similar problem with non-date ranges until
we realized that it wasnt so much th
On May 18, 2004, at 1:43 PM, Timothy Stone wrote:
Erik Hatcher wrote:
Lucene 1.4 (now in release candidate stage) includes built-in sorting
capabilities, so I definitely recommend you have a look at that.
SearchBean is effectively deprecated based on this new much more
powerful feature.
In our application we had a similar problem with non-date ranges until
we realized that it wasnt so much that we were searching for the
values in the range as restricting the search to that range, and then
we used an extension to the org.apache.lucene.search.Filter class, and
our implementation got
Thanks, I'll try that. It would nice too if I could extend field (it
is a final class) and create a numerical field. Is that not desirable?
Claude
On May 18, 2004, at 12:06 PM, Ype Kingma wrote:
On Tuesday 18 May 2004 19:38, Claude Devarenne wrote:
Hi,
I have over 60,000 documents in my index w
Certainly any advancement in this area seems like a good idea.
I'll throw a use case on the pile as well. For my own interest, the
biggest need is in highlighting (i.e. highlighting relevant segments within
the full text of documents). I need to provide highlighted abstracts in
the search resu
On Tuesday 18 May 2004 19:38, Claude Devarenne wrote:
> Hi,
>
> I have over 60,000 documents in my index which is slightly over a 1 GB
> in size. The documents range from the late seventies up to now. I
> have indexed dates as a keyword field using a string because the dates
> are in MMDD for
+1
- Original Message -
From: "Kevin Burton" <[EMAIL PROTECTED]>
To: "Lucene Users List" <[EMAIL PROTECTED]>
Sent: Tuesday, May 18, 2004 2:43 PM
Subject: Internal full content store within Lucene
> Per the discussion the other day about storing content external to
> Lucene I think we h
Per the discussion the other day about storing content external to
Lucene I think we have an opportunity to improve the lucene core and
bring a lot of functionality to future developers.
Right now Lucene allows you to have a 'stored' field which keeps the
content with a segment along with your
Erik Hatcher wrote:
Lucene 1.4 (now in release candidate stage) includes built-in sorting
capabilities, so I definitely recommend you have a look at that.
SearchBean is effectively deprecated based on this new much more
powerful feature.
Erik
Forgive my naivety, but isn't the purpose of
Hi,
I have over 60,000 documents in my index which is slightly over a 1 GB
in size. The documents range from the late seventies up to now. I
have indexed dates as a keyword field using a string because the dates
are in MMDD format. When I do range queries things are OK as long
as I don't
Is there anyone out there that has page ranking implemented on top of
Lucene?
Just in case anyone may be thinking otherwise, when I say page ranking
I'm not referring to the ranking of results from searches. I'm talking
about something similar to how google computes what page may be more
relevan
Lucene 1.4 (now in release candidate stage) includes built-in sorting
capabilities, so I definitely recommend you have a look at that.
SearchBean is effectively deprecated based on this new much more
powerful feature.
Erik
On May 18, 2004, at 11:42 AM, Timothy Stone wrote:
Lucene Us
Lucene Users,
I'm using the SearchBean contribution from the sandbox to implement a
Struts application search with Lucene (taking ACO's advice and going MVC
on the demo app.)
Right now I'm having a problem with using any Document objects that
might be available and getting an IOException.
So b
Hi!
I'm having some trouble with an index of mine. Basically, I'm having a
content managment system with a timertask that regularily triggers an
indexing method. This method indexes content that has been added to the
CMS since last excecution of the indexing method. This all works fine...
Or so it
People frequently have problems when using Lucene with Tomcat. I
recall somebody mentioning some security policy. I use Jetty and don't
have such issues.
Regarding creating lock dir if it doesn't exist - sure. I think we
have a bug open in Bugzilla for that issue.
Otis
--- Grant Ingersoll <[EM
20 matches
Mail list logo
