B-Trees and Inverted Index – De facto standard for file organization (II)
In the context of modern IR Systems, using a dictionary or hash table to represent inversion list would be kind of tedious as it request huge amount of memory. There for its obvious that we need to get the help of secondary storage to store the content and retrieve when required. Then again there is a huge overhead of using secondary storage to store and read a dictionary. So the solution that we came across was B-Tree, which is a used almost each and every implementation of inverted index. Definition of a B-Tree of order ‘m’ A root node with 2 ~ 2m keys All the other internal nodes have between m ~ 2m keys All keys are kept in ascending order All levels have the same level of differ (at most 1) e.g: Inversion lists structures are used because they provide optimum performance in searching large databases. The optimality comes from the minimization of data flow in resolving a query. Only data directly related to the query are retrieved from secondary storage. The beauty of B-Trees lie...