Marco Schmidt writes:
> I'm trying to find out whether Lucene is an option for a project of
> mine. I have texts which also have a date and a list of numbers
> associated with each of them. These numbers are ID values which connect
> the article to certain categories. So a particular article X m
Hi
Can u share the searcher.search(query, hitCollector); [light weight paging
api ]
Code on the form ,may be somebody like me need's it.
; )
Karthik
-Original Message-
From: Praveen Peddi [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 22, 2004 1:24 AM
To: Lucen
This, of course, isn't the right forum for this question...
Not to encourage off-topic posts, but I just happened to know at least
part of the answer since we just went through the same issue.
First thing to do is to make sure you are setting these properties
before the first URLStreamHandler fo
Hi FYI,
I am doing web crawling in my application using proxy setting. like the
below code..
Properties systemSettings = System.getProperties();
systemSettings.put("http.proxySet", "true");
systemSettings.put("http.proxyHost",
profileBean.getProfileParamBean().getProxyHost().trim());
sys
I'm trying to find out whether Lucene is an option for a project of
mine. I have texts which also have a date and a list of numbers
associated with each of them. These numbers are ID values which connect
the article to certain categories. So a particular article X might
belong to categories 17,
If it is unindexed, then you cannot query on it, so you do not have a
choice. The other option is to use a field that is indexed, not
tokenized, and not stored (you have to use new Field(...) to accomplish
that) if you don't want to store the field data.
Erik
On Sep 21, 2004, at 5:54 P
is it most effecient to index or not index 'numeric' ranges that i
will do a range search byepoc_date:[110448 TO 820483200]
would be be better to treat it as Field.Keyword or Field.UnIndexed ?
--
___
Chris Fraschetti, Student CompSci Sys
The way we do it is: Get all the document ids, cache them and then get the
first 50, second 50 documents etc. We wrote a light weight paging api on top
of lucene. We call searcher.search(query, hitCollector); Our
HitCollectorImpl implements collect method and just collects the document id
only.
On Tuesday 21 September 2004 21:33, Chris Fraschetti wrote:
> I was wondering was the best way was to go about returning say
> 1,000,000 results, divided up into say 50 element sections and then
> accessing them via the first 50, second 50, etc etc.
>
> Is there a way to keep the query around so th
The best first approach is to simply re-query every time the user goes
to a new page, keeping around the query in some for or another (perhaps
the expression if you're using QueryParser) and the page number.
If that is fast enough, then you're done! :)
If it is not, then you could consider cach
I was wondering was the best way was to go about returning say
1,000,000 results, divided up into say 50 element sections and then
accessing them via the first 50, second 50, etc etc.
Is there a way to keep the query around so that lucene doesn't need to
search again, or would the search be cached
Hello everyone,
I'm trying to use Lucene in a webproject to search for products. The problem is that I
have to display the search results grouped by category. There are about 500.000
products and every product belongs to a category. There are 150 categories. Now for
every search I would like to
Luceners,
I'm using SnowBallAnalyzer for spanish. I'm indexing and
searching with these analyzer, but when I open luke and look up the
document with standardAnalyzer (I don't know how to use snowBallAnalyzer
in spanish in Luke) I see the tokens in case sensitive and I see the
word "tarea" i
Try setUseCompoundFile(false) on your IndexWriter as soon as you create
it or before you call optimize
-Original Message-
From: Christian Rodriguez [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 21, 2004 1:10 PM
To: Lucene Users List
Subject: Re: Problems with Lucene + BDB (Berkeley D
Andy, you are right.
I tried with Lucene 1.3 and it worked perfectly. This should be added
to a README in the Lucene + BDB sandbox (or somewhere) so people dont
spend days struggling with those weird non - deterministic bugs I am
getting...
Now, I do need to use version 1.4, so Id like to see if
I have this query string
queryString = tarea AND (tipo:contact OR tipo:account OR
tipo:opportunity OR tipo:event OR tipo:task)
and when I parse
query=MultiFieldQueryParser.parse(queryString,fields,analyzer);
I got one letter less. I have "tarea" and the MultiFieldQueryParser
change to "tare". I don
16 matches
Mail list logo
