--
You received this message because you are subscribed to the Google Groups "NOSQL" group.
To post to this group, send email to nosql-di...@googlegroups.com.
To unsubscribe from this group, send email to nosql-discussi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nosql-discussion?hl=en.
When people think of MarkLogic they often think of its text search capabilities. Thefounding team has a deep background in search: Chris Lindblad was the architect of theUltraseek Server, while Paul Pederson was the VP of Enterprise Search at Google.MarkLogic supports numerous search features including word and phrase search, booleansearch, proximity, wildcarding, stemming, tokenization, decompounding, case-sensitivityoptions, punctuation-sensitivity options, diacritic-sensitivity options, document qualitysettings, numerous relevance algorithms, individual term weighting, topic clustering,faceted navigation, custom-indexed fields, and more.
sphinx?
--
http://tarantool.org - an efficient, extensible in-memory data store
Based on Lucene and with all its power but also operationally simple
and scales out really well.
//Martin
> --
> You received this message because you are subscribed to the Google Groups
> "NOSQL" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/nosql-discussion/-/wmIYIXk5OrUJ.
Those two choices are apples and oranges.
Redis is a simple, fast key store that allows you to build your own
reverse index.
Lucene/Hyperdex/MarkLogic/Sphinx/... *ARE* text oriented reverse indexes.
Choose whichever you need!
Good luck!
-brian
>> it comes to building& searching inverted indices?
>>
>> Thanks so much,
>> J
Ran
> --
> You received this message because you are subscribed to the Google Groups "NOSQL" group.
If you're doing this to learn and have a fair bit of exploration into composing various data structures into custom solutions, Redis is quite nice for that since it gives you building blocks that are easy to use.
The bigger, commercial "databases" (nosql or not) all have their own, baked-in approaches to dealing with things so it's more of a question of whether they fit your needs or not based on how/what they implement under the hood.
So, without knowing a lot more about what you're trying to do, it's hard to say much more.
Have fun,
John