The R*-tree: an efficient and robust access method for points and rectangles
SIGMOD '90 Proceedings of the 1990 ACM SIGMOD international conference on Management of data
R-trees: a dynamic index structure for spatial searching
SIGMOD '84 Proceedings of the 1984 ACM SIGMOD international conference on Management of data
Novel Approaches in Query Processing for Moving Object Trajectories
VLDB '00 Proceedings of the 26th International Conference on Very Large Data Bases
On the Generation of Spatiotemporal Datasets
SSD '99 Proceedings of the 6th International Symposium on Advances in Spatial Databases
Indexing the Current Positions of Moving Objects Using the Lazy Update R-tree
MDM '02 Proceedings of the Third International Conference on Mobile Data Management
ICDE '06 Proceedings of the 22nd International Conference on Data Engineering
Supporting frequent updates in R-trees: a bottom-up approach
VLDB '03 Proceedings of the 29th international conference on Very large data bases - Volume 29
Indexing Moving Objects Using Short-Lived Throwaway Indexes
SSTD '09 Proceedings of the 11th International Symposium on Advances in Spatial and Temporal Databases
Thread-level parallel indexing of update intensive moving-object workloads
SSTD'11 Proceedings of the 12th international conference on Advances in spatial and temporal databases
Parallel main-memory indexing for moving-object query and update workloads
SIGMOD '12 Proceedings of the 2012 ACM SIGMOD International Conference on Management of Data
Boosting moving object indexing through velocity partitioning
Proceedings of the VLDB Endowment
Hi-index | 0.00 |
Update-intensive applications, such as location-aware services, sensor networks, and stream databases, face with the problem of frequent updating. R-tree and its variants are dominant indexing structures for multi-dimensional object. An update in R-tree traditionally consists of a deletion and an insertion, which is sometimes inefficient. In this paper, we present an R-tree-based index structure called RUM+-tree for enabling efficient frequent updates. In RUM+-tree, compared to R-tree, two additional data structures are maintained: an Update Memo and a hash table. An object's leaf node can be accessed directly through the hash table and the Update Memo records the versioning information of the most recent data. The idea of RUM+-Tree is to deal with updates locally in a bottom-up manner as often as possible. Only when the update involves multiple MBRs, a multi-version solution is utilized for acceleration. Compared to RUM-tree [1], RUM+-tree can reduce the new version to be created. Thus, it can accelerate the garbage clean and update procedure. Compared to LUR-tree [5], RUM+-tree eliminates traditional updates like used by R-tree completely. Our experimental results show that our technique outperforms RUM-tree and LUR-tree significantly.