I'm starting with Lucene 4 and have built my own analyzer with stemming
and synonyms. This works perfectly.
I built a Lucene index with several documents (with an ID) containing a
text (with TextField) and a list of words or expressions related to the
text (a kind of tag). Everything is OK
hi Nicolas ,
if i understand correctly what you are describing is that your tag field
will contain Lucine queries syntax - one word = exact match , 2 words xx
yy = phrase match , and so on .
there is a search method called Prospective search which fits this
situation .
you can try and use this
Just for the record, the solution that I adopted is as follows:
- Create a setType(String field, String type) and call it for any known
numeric fields, before adding any document. This method saves
the type definition in a file and also sets the MapString,NumericConfig
that is used in the
I've built a search prototype feature for my application using Lucene, and it
works great. The application monitors a remote system and currently indexes
just a few core attributes of the objects on that system. I get notifications
when objects change, and I then update the Lucene index to
Drew Kutcharian wrote:
I'm trying to figure out what would be a better approach to
indexing when it comes to a large number of records (say 1 billion)
A rule of thumb is that if you want a list of exact matches use a database. If
you want a ranked list of matches use Lucene.
-- Andrew
Thanks to all! I'll see your links and I'll tell you.
Thanks again :D
Date: Wed, 6 Feb 2013 14:22:30 +0530
Subject: Re: How to implement Lucene
From: ping.swap...@gmail.com
To: java-user@lucene.apache.org
Hi,
Try to use solr with DIH (Data import handler). It can import data from
Hi Thomas,
On Wed, Feb 6, 2013 at 2:50 PM, Becker, Thomas thomas.bec...@netapp.com wrote:
I've built a search prototype feature for my application using Lucene, and it
works great. The application monitors a remote system and currently indexes
just a few core attributes of the objects on
Just to be sure what you are trying to do:
A) compare the relevance of different similarities? this is something
the benchmark.quality package (actually pretty much unrelated from the
rest of the benchmark package!) does, if you have some e.g. TREC
collection or whatever to test with.
B) compare
Hello,
I have an application where a great many documents may not have any
terms after StandardAnalyzer has had its way with the body. In that
case, depending on some other metadata, I may not wish to add the
document to the index altogether. Is there a way to tell?
i.e., current I'm doing this: