Hi,
I have two web applications that uses lucene 2.3.2. Both share the same
index and can write or read. Writing is synchronized based on file system to
allow only one IndexWriter to work at the moment. There can be multiple
IndexReader. IndexReader is stored and before searching, there is done
#re
(sorry for picking this up so late...)
This sounds like a perfect fit for document DBs like CouchDB and MongoDB
- based on your architecture and data structure.
They are designed for multi-server applications, and use Map/Reduce
which will give you Lucene operations directly from your DB, n
How large is (large)? What machines are you intending to run this on?
In general, though, don't worry about index size until you actually have some
numbers to deal with. Solr generally has resource issues based on the number
of #unique# terms in an index. So repeating the same thing in a bunch of
Hi,
I have several documents that share the same (large) searchable data.
For example, say my Documents represent movies, and 2 movies share the same
actorBiography of Brad Pitt (assuming I want
to search movies by actorBiography words, far-fetched as it might seem):
Document1:
- movieName=
Hi,
can I know, if there is any improvement since 4 years ?
Can we do that now in Lucene 3.0.3 ?
--
View this message in context:
http://lucene.472066.n3.nabble.com/spell-checker-across-multiple-fields-tp539392p2654706.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
