2015 IEEE 31st International Conference on Data Engineering 2015
DOI: 10.1109/icde.2015.7113307
|View full text |Cite
|
Sign up to set email alerts
|

Bi-temporal Timeline Index: A data structure for Processing Queries on bi-temporal data

Abstract: Following the adoption of basic temporal features in the SQL:2011 standard, there has been a tremendous interest within the database industry in supporting bi-temporal features, as a significant number of real-life workloads would greatly benefit from efficient temporal operations. However, current implementations of bi-temporal storage systems and operators are far from optimal. In this paper, we present the Bi-temporal Timeline Index, which supports a broad range of temporal operators and exploits the specia… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
67
0

Year Published

2015
2015
2021
2021

Publication Types

Select...
4
3
1

Relationship

1
7

Authors

Journals

citations
Cited by 41 publications
(67 citation statements)
references
References 19 publications
0
67
0
Order By: Relevance
“…Descriptions of "Big Data" systems in production environments typically mention data sizes in the hundreds of TB to hundreds of PB [27,4,17] or trillions to hundreds of trillions of rows [12]. "Big Data" research studies on the other hand tend to work with much smaller datasets, ranging from hundreds of GB [6,18,16,24] to a few TBs [29,28,23,1]. The largest dataset we have seen used in an existing "Big Data" study is 16 TB [9].…”
Section: Related Workmentioning
confidence: 98%
“…Descriptions of "Big Data" systems in production environments typically mention data sizes in the hundreds of TB to hundreds of PB [27,4,17] or trillions to hundreds of trillions of rows [12]. "Big Data" research studies on the other hand tend to work with much smaller datasets, ranging from hundreds of GB [6,18,16,24] to a few TBs [29,28,23,1]. The largest dataset we have seen used in an existing "Big Data" study is 16 TB [9].…”
Section: Related Workmentioning
confidence: 98%
“…HANA supports temporal queries, such as temporal aggregation, time travel and temporal join, based on a unified index structure called the Timeline Index [88], [242], [247]. For every logical table, HANA keeps the current version of the table in a Current Table and the whole history of previous versions in a Temporal Table, accompanied with a Timeline Index to facilitate temporal queries.…”
Section: Sap Hanamentioning
confidence: 99%
“…It provides rich data analytics functionality by offering multiple query language interfaces (e.g., standard SQL, SQLScript, MDX, WIPE, FOX and R), which makes it easy to push down more application semantics into the data management layer, thus avoiding heavy data transfer cost. It supports temporal queries based on the Timeline Index [242] naturally as data is versioned in HANA. It provides snapshot isolation based on multi-version concurrency control, transaction semantics based on optimized two-phase commit protocol (2PC) [243], and fault-tolerance by logging and periodic checkpointing into GPFS file system [148].…”
Section: Sap Hanamentioning
confidence: 99%
“…Given the structural similarity and the wide recognition, TPC-C has been used for this purpose, e.g., in [2]. We also used a similar approach (with additional timestamp assignment) in a previous version of the benchmark [8], but this proved to not be fully adequate: The set of update scenarios is quite small, and does not provide much emphasis on temporal aspects such as timestamp correlations. The query mix also constrains the flexibility in terms of temporal properties, e.g., since a fixed ratio of updates needs to go to specific tables.…”
Section: Benchmark Datamentioning
confidence: 99%