ITISS: an efficient framework for querying big temporal data

Zhongpu Chen, Bin Yao, Zhi-Jie Wang, Wei Zhang, Kai Zheng, Panos Kalnis, Feilong Tang

Research output: Contribution to journalArticlepeer-review

4 Scopus citations


In the real word, temporal data can be found in many applications, and it is rapidly increasing nowadays. It is urgently important and challenging to manage and operate big temporal data efficiently and effectively, due to the large volume of big temporal data and the real-time response requirement. Processing big temporal data using a distributed system is a desired choice, since a single-machine based system usually has the limited computing ability. Nevertheless, existing distributed systems or methods either are disk-based solutions, or cannot support native queries, which may not well meet the demands of low latency and high throughput. To attack these issues, this article suggests a new approach to handle big temporal data. Our approach is an In-memory based Two-level Index Solution in Spark, dubbed as ITISS. The proposed framework of our solution is easily understood and implemented, but without loss of effectiveness and efficiency. Based on the proposed framework, this article develops targeted algorithms for handling time travel, temporal aggregation, and temporal join queries, respectively. We have implemented our framework in Apache Spark, extended the Apache Spark SQL to support declarative SQL interface that enables users to perform temporal queries with a few lines of SQL statements, and conducted extensive experiments to verify the performance of our solution. The experimental results, based on both real and synthetic datasets, consistently demonstrate that our proposed solution is efficient and competitive for processing big temporal data.
Original languageEnglish (US)
Pages (from-to)27-59
Number of pages33
Issue number1
StatePublished - May 22 2019


Dive into the research topics of 'ITISS: an efficient framework for querying big temporal data'. Together they form a unique fingerprint.

Cite this