Proceedings of Semantic Web Information Management on Semantic Web Information Management 2014
DOI: 10.1145/2630602.2630610
|View full text |Cite
|
Sign up to set email alerts
|

Using Graph Summarization for Join-Ahead Pruning in a Distributed RDF Engine

Abstract: The need for scalable and efficient RDF stores has seen a high demand recently. Many efficient systems, both centralized and distributed, have been proposed. Since a row-oriented output is required by SPARQL, most of the current systems rely on relational joins. One of the problems with relational joins, though, is a performance bottleneck imposed by the generation of large intermediate relations which could be avoided by using more accurate data and pruning statistics. To address this problem, recently severa… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2015
2015
2020
2020

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 6 publications
(4 citation statements)
references
References 15 publications
0
4
0
Order By: Relevance
“…Nodes and edges are summarized according to their frequencies and/or based on ontology patterns in [28,33]. Summaries where nodes are grouped by graph clustering [20], user-defined aggregation rules [34], mining [9], and identification of frequent subtrees [39] do not reflect the complete structure, and/or require user input. With different objectives, these summaries may omit part of the graph structure, or be much too large for visualization.…”
Section: Related Work and Conclusionmentioning
confidence: 99%
“…Nodes and edges are summarized according to their frequencies and/or based on ontology patterns in [28,33]. Summaries where nodes are grouped by graph clustering [20], user-defined aggregation rules [34], mining [9], and identification of frequent subtrees [39] do not reflect the complete structure, and/or require user input. With different objectives, these summaries may omit part of the graph structure, or be much too large for visualization.…”
Section: Related Work and Conclusionmentioning
confidence: 99%
“…The architecture of our SPARQL 1.1 engine (in the following coined TriAD*) is based on TriAD [11,12], which we originally developed for processing conjunctions of triple patterns in SPARQL 1.0. The design of TriAD in principle follows a classical master-slave architecture at indexing time, but allows for a direct, asynchronous communication among the slaves at query-processing time.…”
Section: Architecturementioning
confidence: 99%
“…To overcome bisimulation issues, [5] suggests locality-based summaries, whose generation requires removing the (many) triples whose objects are literals from the input graph. Our summaries represent the queries over these triples as well.…”
Section: Related Workmentioning
confidence: 99%