Sergey, I don't think you missed anything (unless you count a number of nice features that Solr has that you didn't explicitly list) - Solr indeed sounds like a good fit.
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Sergey Nikitin <[EMAIL PROTECTED]> > To: solr-user@lucene.apache.org > Sent: Sunday, September 14, 2008 5:07:27 PM > Subject: Is Solr suitable for my application? > > > Hello everyone, > > In our web app we got about 10 million of documents, structure of document > is (only what is important for searching): > ~10 Short fields (20 chars max) > 1 Long field - represents content of the document, stored as xml. On average > about 50k chars in xml, with about 500 chars of important text data to be > indexed. > > Updating/creating of document is a frequent operation, deleting is not > frequent. > > Now we are using indexing functionality of our DBMS and it is not as good as > we want (slow, depend on concrete DBMS, additional load on DBMS, not > scalable, etc). So, we want to switch to some other solution. > > Most important requirements are: > functionality - searching by attribute / all attributes, filters, sorting, > synonyms, etc... > performance - at least faster that current solution. > scalability - data and load may grow up, there should be easy way to support > it. > > Preferable tradeoffs: > + faster queries > - less frequent update (flushing changes once per 24 hours is ok) > - bigger index size > > It seems that Solr fits perfectly - a lot of cool features, fast, good > scaling support. > > Maybe I've missed something important? > > Any suggestions would be appreciated. > Thanks, > Sergey > -- > View this message in context: > http://www.nabble.com/Is-Solr-suitable-for-my-application--tp19484366p19484366.html > Sent from the Solr - User mailing list archive at Nabble.com.
