database - Storage of sparse numerical data (e.g. inverted index) - any conventions? -
Is there any acceptable way of storing and accessing scarce numerical data (such as by the search engine's inverted index / term matrix)? An RDBMS looks unfair to such data, but it would be good to store it in any database (saved on disk, running as server, etc.). Is there an accepted solution to this kind of problem (such as the current model capable of supporting such models)? Does anybody know how Google stores and accesses its indexes so fast?
For more information and links to more information, take a look here.
Comments
Post a Comment