If all you do is exact match, you can create non-unique indexes on
columns, or functional indexes.
If the database index is optimal, there should not be much performance
difference between database approach vs Lucene approach.
Lucene's inverted index is just one kind of data structure for quick
data access. For your exact matching, it may not help much.
Creating and maintaining Lucene index is surely more coding than create
a database index though.
--
Chris Lu
-------------------------
Instant Scalable Full-Text Search On Any Database/Application
site: http://www.dbsight.net
demo: http://search.dbsight.com
Lucene Database Search in 3 minutes:
http://wiki.dbsight.com/index.php?title=Create_Lucene_Database_Search_in_3_minutes
DBSight customer, a shopping comparison site, (anonymous per request) got 2.6
Million Euro funding!
s_kumar wrote:
The requirement is to perform a Quick search on a DB table that has more than
a million real estate property records where the primary search criteria is
state/city, state/county or zip code. How can I use lucene effectively in
this case ? Which one will be better a plain sql search on the DB table or a
lucene search with some sort of a index constructed (not sure how to go
about this) ?
Please Advice.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
