2018
DOI: 10.1007/978-3-319-94809-6_12
|View full text |Cite
|
Sign up to set email alerts
|

ChronoGraph: A Versioned TinkerPop Graph Database

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(6 citation statements)
references
References 22 publications
0
6
0
Order By: Relevance
“…Since temporal graphs can grow very large in size, the questions of secondary storage are crucial. In this context, one can develop a temporal graph management system by designing a dedicated storage engine such as a file system layout [17] or a temporal key/value store [18]. However, regarding the fact that most real-world temporal graphs are more likely to exponentially grow in size, the backend storage engine should offer scalability.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…Since temporal graphs can grow very large in size, the questions of secondary storage are crucial. In this context, one can develop a temporal graph management system by designing a dedicated storage engine such as a file system layout [17] or a temporal key/value store [18]. However, regarding the fact that most real-world temporal graphs are more likely to exponentially grow in size, the backend storage engine should offer scalability.…”
Section: Related Workmentioning
confidence: 99%
“…These methods are mainly motivated by concepts of logging and checkpointing which reflects on lessons learned from classical techniques of database state recovery [23], [24]. The Log approach followed by Raphtory [25], ChronoGraph [26] and TAG [5], [6] consists of storing graph updates as a series of timestamped logs such that any graph state can be recovered by reloading all logs with a relative timestamp lower than or equal to the requested one. Whereas the Copy approach consists of materializing and persisting graph snapshots.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Tracking this history requires a fitting data structure: thankfully, there has been a recent push towards adding temporal capabilities to graph databases, with the ability to efficiently store and navigate the history of an entire labelled attributed graph. Two examples include Greycat [18] and ChronoGraph [17].…”
Section: Storage and Retrieval Of Historic Datamentioning
confidence: 99%
“…Real graphs, however, are dynamic [12] such that their topology is subject to continuous changes. In this context, a new emphasis is being placed to support time as a first class citizen in graph management systems [13,14,15,16]. Most of these systems rely on real-world temporal graphs to evaluate their proposed methods.…”
Section: Introductionmentioning
confidence: 99%