Live data from Hacker News

Full Text Search in Mongo

mongodb.org

1–10 of 15 posts

Re: Full Text Search in Mongo

#3

Yes, do you have a question or point to make about MongoDB fts?

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 algorithms are appliable and clusterable over NOSQL databases, and which ones can do this without dumping the entire database.

I had some links talking about it:

Full text search with MongoDB[2]

Ask HN: What's the best way to handle full-text search with MongoDB?[3]

AskHN: NoSQL with full text search - which is better CouchDB or MongoDB?[4]

Is MongoDB a valid alternative to relational db + lucene?[5]

[1] http://schedule.sxsw.com/events/event_IAP7455

[2] http://hmarr.com/2010/mar/18/full-text-search-with-mongodb/

[3] http://news.ycombinator.com/item?id=2069271

[4] http://news.ycombinator.com/item?id=1984666

[5] http://stackoverflow.com/questions/2546494/is-mongodb-a-vali...

[6] http://engineering.foursquare.com/2011/03/22/building-a-reco...

Re: Full Text Search in Mongo

#5
This 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 see a MongoDB component that replicates data from the oplog to a dedicated full-text store like Lucene or Solr.

Re: Full Text Search in Mongo

#6

This 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…

How are you doing your tokenization and stemming? I find it hard to believe that the actual token lookup is slower.

Re: Full Text Search in Mongo

#7

This 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…

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.

Re: Full Text Search in Mongo

#8
As others have mentioned, this isn't really true full-text search support, but instead an old page with an example of how you can get that kind of functionality.

Full-text search should be coming, but it's still a ways off... The most recent word from a 10gen employee is that it "Seems likely to be in 2.2."

You can keep up with the status of true full-text search here:

http://jira.mongodb.org/browse/SERVER-380

Re: Full Text Search in Mongo

#9
post #8

As others have mentioned, this isn't really true full-text search support, but instead an old page with an example of how you can get that kind of functionality. Full-text search should be coming, but it's still a ways off... The most recent word from a 10gen employee is that it "Seems likely to be in 2.2." You can keep up with the status of true full-text search here: http://jira.mongodb.org/browse/SERVER-380

Thanks, great to know it's being considered as part of the product roadmap.

Re: Full Text Search in Mongo

#10

Yes, do you have a question or point to make about MongoDB fts?

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?

Post reply on HN