We have many different types of objects that we are indexing with Lucene
(coupons, roadtrips, events, attractions, etc).
Because events and coupons can expire, we would like to apply a date filter to
the query to filter out the expired items, but the problem is that there are
other objects l
I just add a 1000 to it, but in my rounding, I always make sure that I have 4
decimal places.
Here are some code snippets;
//indexing the lat
double lat = physicalAddress.getLatitude() + 1000.0;
Double latitude = new Double(lat);
document.add(new Field(Indexer.LATITUDE, latitude.toString()
-
From: "Daniel Naber" <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Tuesday, February 27, 2007 5:33:01 PM (GMT-0500) America/New_York
Subject: Re: indexing and searching the document title question
On Tuesday 27 February 2007 23:07, Phillip Rhodes wrote:
> NAME:
he same data multiple
times, once for searching and once for displaying. So you'll search
on the lowercased, indexed field and display the UN_TOKENIZED
version since it'll retain the capitalization.
7> I think your underlying problem is that the syntax of the search
isn't correct. Yo
I am doing this, but for 16000+ records.
I indexed each document with the lat/long values as keywords. I added a 1000
to each value to get it into the positive range.
I do a range query for the lat long, calculating the min/max for the long/lat
from the origination point. Don't forget to add
Hi,
According to the FAQ, by indexing the title of the document and performing a
search against the shorter field will automatically give it a higher weight
than matches against the document content. That is what I am trying to
accomplish with a "NAME" field. If someone enters a close match of
I have a query that can return documents that represent different types of
things (e.g. books, movies, coupons, etc)
There is a "object_type" keyword on each document, so I can tell that a
document is a coupon or a book etc...
The problem is that I need to display a count of each item type tha
Mohammad,
According to the responses on this thread, there appears to be no
performance benefit to using multiple instances of IndexSearcher
Unless I hear otherwise, there is no point in creating such a pool.
Phillip
Mohammad Norouzi wrote:
Hi
would you tell how we can create a searcher pool
I was tarring up a james installation, and there are an awful lot of
files in the /var/mail/spam, the /var/mail/address-error, and some other
folders. Is this stuff that james deletes on a regular basis, or should
I do a regular "pruning" of the different files that james stores?
Does anyone
I understand that "Documents are the primary retrievable units from a
Lucene query" But I don't know if I want to have 12 documents in the
lucene index that represent the same business object, or if I should
place 12 different business documents within the lucene index.
Here is the backgroun
10 matches
Mail list logo