News for hackers. Stuff that matters.
Re:AskHN: NoSQL with full text search - which is better Couc... by abiczo on Wednesday December 08, 2010 @07:36PM (#1985411)
I wouldn't rule out using a separate search engine. Yes, you'll probably have to keep the index in sync with the db manually but I found that it also gives you much more flexibility.

I personally use Solr with MongoDB and it works pretty well. Keeping the index in sync is not that big of a deal for me (depends on the application of course) and in exchange I get a full featured FTS engine that is probably more mature and has more features than an integrated one would have.

Re:AskHN: NoSQL with full text search - which is better Couc... by andrewstuart on Thursday December 09, 2010 @10:41PM (#1990502)
Forgive the noob question, but how does the integration work? Can you do a full text search combined with selection criteria on other database fields?
Re:AskHN: NoSQL with full text search - which is better Couc... by datd00d on Wednesday December 08, 2010 @07:56PM (#1985491)
how are you going about syncing? And what is your average document size (bytes, as well as attributes/elements)
Re:AskHN: NoSQL with full text search - which is better Couc... by abiczo on Thursday December 09, 2010 @04:15AM (#1986727)
The syncing is done on the app level: when a new document is inserted into the db that needs to be indexed a background job is launched that insert the document in Solr. This shouldn't be too hard manage if you can write post-save handlers in your model code.

The average document is about 1KB and has about 30 attributes (but only 2-3 of those attributes needs to be index).