Earlier quoted context omitted.
How are you doing your tokenization and stemming? I find it hard to believe that the actual token lookup is slower.
Tokenization was a simple string split on whitespace, and no stemming. It was quite a large Mongo dataset, so only a fraction of the index and data would've been in memory, it could've easily been quicker for a smaller dataset living in memory. For me, one of the benefits of Lucene is the powerful built-in query parsing, tokenization, analyzers, etc.
Full Text Search in Mongo
11–15 of 15 posts
Re: Full Text Search in Mongo
#12Re: Full Text Search in Mongo
#13Earlier quoted context omitted.
More like throwing some wood into the fire. Was instigated by the talk[1] "Solr Power FTW", and "Building a recommendation engine, foursquare style" [6] (where Justin Moore admits: We are dumping the data from Mongo and loading it into Hadoop over S3 files. Map reduce is in this system, not in our mongo databases. ). Was wondering how much has this evolved over the last 6 months, how viable machine learning algorithm…
The question regarding the difference between CouchDB and Mongo wasn't fully explored. Can someone here comment one which route makes more sense right now? Riak also seems to have full-text search. Has anyone used it?
Riak isn't the fastest single node system, but if you're going big and need several servers anyway it will save you some time.
CouchDB could use elasticsearch and its streaming indexation ("river" -> http://www.elasticsearch.org/docs/elasticsearch/river/couchd... ) to get scalable fulltext search.
An interesting project for fulltext search when it comes to mongodb and SOLR is photovoltaic ( https://github.com/mikejs/photovoltaic ), it pipes the mongoDB changes to the Solr XML interface. Sadly, I haven't had time to use it yet, but it looks interesting.
Re: Full Text Search in Mongo
#14This isn't really supposed to be a proper full-text index feature, instead it's building a rudimentary inverted index using a string array property. It's possible to create indexes over array properties in MongoDB, which is very cool, and increases performance to an extent. But even with an index, this approach to full-text was much slower for me than an equivalent search against the same data in Lucene. I'd love to…
Photovoltaic does this: https://github.com/mikejs/photovoltaic
I haven't had time to play arround with it yet though :(
Re: Full Text Search in Mongo
#15i was very excited by this technology. i tried to implement it on a large database. it bombed, the hype around nosql kind of whitewashes the fact that at the end, it is indexed in a btree, exactly how mysql would do it. i am not trashing mongodb, i am a big fan of it, i am just making a point about being objective.