Demo Data from EDBT 2026 / reviewers in the wild / expert
Yuval Linker
dblp:417/2714
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2025
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 1 · 1 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Databases, data mining, and information retrieval
1 paper |
Graph data management · 33% Query processing and optimization · 33% Indexing and storage engines · 33% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Graph data management
graph query processing |
0.9 | 1 | 2025 | CompactLTJ: Space & Time Efficient Leapfrog Triejoin on Graph Databases · VLDB J. 2025 |
Indexing and storage engines
succinct data structures |
0.9 | 1 | 2025 | CompactLTJ: Space & Time Efficient Leapfrog Triejoin on Graph Databases · VLDB J. 2025 |
Query processing and optimization › join processing › join algorithms
worst-case optimal join |
0.9 | 1 | 2025 | CompactLTJ: Space & Time Efficient Leapfrog Triejoin on Graph Databases · VLDB J. 2025 |
Methods — techniques the papers use, named apart from their topics
leapfrog triejoin · 0.9compact tree representation · 0.9
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | CompactLTJ: Space & Time Efficient Leapfrog Triejoin on Graph DatabasesabstractAbstract Leapfrog Triejoin (LTJ) is arguably the most practical and popular worst-case-optimal (wco) algorithm for solving basic graph patterns in graph databases. Its main drawback is that it needs the database triples (subject, predicate, object) represented as paths in a trie, for each of the six orders of subject, predicate, and object. The resulting blowup in space makes most systems disregard LTJ or implement it only partially, which makes their corresponding algorithms non-wco. In this paper we show that, by using compact data structures, it is possible to build an index that at the same time matches the query time performance of the fastest classic wco index, and uses a fraction of the space of non-wco indices (which are much slower). Concretely, we make use of compact tree representations to store functional tries using one bit per trie edge, instead of one pointer, and further reduce the space by storing partial tries. Our most compact variant uses 5–6 times less space than classic wco implementations and 2–3 times less than classic non-wco systems. At solving queries, it is on par with the fastest classic wco system, and 30–40 times faster than non-wco systems. We further incorporate improved query resolution strategies into CompactLTJ variants, which makes it considerably faster than classic wco systems as well, on queries that do not output too many results. Finally, we show how CompactLTJ can incorporate dynamism without altering its performance, even under very demanding update regimes. We leave a public fully-functional implementation of CompactLTJ that can be directly used by practitioners. Diego Arroyuelo, Daniela Campos, Adrián Gómez-Brandón, Yuval Linker, Gonzalo Navarro 0001, Carlos Rojas 0002, Domagoj Vrgoc |
VLDB J. | 4 |