The Ring: Worst-case Optimal Joins in Graph Databases using (Almost) No Extra Space

dc.catalogadorgjm
dc.contributor.authorArroyuelo Billiardi, Diego Gastón
dc.contributor.authorGómez-Brandón, Adrián
dc.contributor.authorHogan, Aidan
dc.contributor.authorNavarro, Gonzalo
dc.contributor.authorReutter de la Maza, Juan
dc.contributor.authorRojas-Ledesma, Javiel
dc.contributor.authorSoto, Adrián
dc.date.accessioned2024-05-23T17:13:44Z
dc.date.available2024-05-23T17:13:44Z
dc.date.issued2024
dc.description.abstractWe present an indexing scheme for triple-based graphs that supports join queries in worst-case optimal (wco) time within compact space. This scheme, called a ring, regards each triple as a cyclic string of length 3. Each rotation of the triples is lexicographically sorted and the values of the last attribute are stored as a column, so we obtain the order of the next column by stably re-sorting the triples by its attribute. We show that, by representing the columns with a compact data structure called a wavelet tree, this ordering enables forward and backward navigation between columns without needing pointers. These wavelet trees further support wco join algorithms and cardinality estimations for query planning. While traditional data structures such as B-Trees, tries, and so on, require 6 index orders to support all possible wco joins over triples, we can use one ring to index them all. This ring replaces the graph and uses only sublinear extra space, thus supporting wco joins in almost no space beyond storing the graph itself. Experiments querying a large graph (Wikidata) in memory show that the ring offers nearly the best overall query times while using only a small fraction of the space required by several state-of-the-art approaches. We then turn our attention to some theoretical results for indexing tables of arity d higher than 3 in such a way that supports wco joins. While a single ring of length d no longer suffices to cover all d! orders, we need much fewer rings to index them all: O(2d) rings with a small constant. For example, we need 5 rings instead of 120 orders for d=5. We show that our rings become a particular case of what we dub order graphs, whose nodes are attribute orders and where stably sorting by some attribute leads us from an order to another, thereby inducing an edge labeled by the attribute. The index is then the set of columns associated with the edges, and a set of rings is just one possible graph shape. We show that other shapes, like for example a single ring instead of several ones of length d, can lead us to even smaller indexes, and that other more general shapes are also possible. For example, we handle d=5 attributes within space equivalent to 4 rings.
dc.fechaingreso.objetodigital2024-08-30
dc.format.extent45 páginas
dc.fuente.origenORCID
dc.identifier.doi10.1145/3644824
dc.identifier.urihttps://doi.org/10.1145/3644824
dc.identifier.urihttps://dl.acm.org/doi/10.1145/3644824
dc.identifier.urihttps://repositorio.uc.cl/handle/11534/85769
dc.information.autorucEscuela de Ingeniería; Reutter de la Maza, Juan; 0000-0002-2186-0312; 126898
dc.information.autorucEscuela de Ingeniería; Arroyuelo Billiardi, Diego Gastón; S/I; 1321287
dc.issue.numero2
dc.language.isoen
dc.nota.accesoContenido parcial
dc.revistaACM Transactions on Database Systems
dc.rightsacceso restringido
dc.subjectWorst-case optimal joins
dc.subjectGraph patterns
dc.subjectGraph databases
dc.subjectGraph indexing
dc.subjectColumn stores
dc.subjectWavelet trees
dc.subject.ddc600
dc.subject.deweyTecnologíaes_ES
dc.titleThe Ring: Worst-case Optimal Joins in Graph Databases using (Almost) No Extra Space
dc.typeartículo
dc.volumen49
sipa.codpersvinculados126898
sipa.codpersvinculados1321287
sipa.trazabilidadORCID;2024-05-20
Files
Original bundle
Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
The Ring - Worst-case Optimal Joins in Graph Databases using (Almost) No Extra Space.pdf
Size:
3.56 KB
Format:
Adobe Portable Document Format
Description: