Proceedings of the 13th International Conference on Database Theory 2010
DOI: 10.1145/1804669.1804675
|View full text |Cite
|
Sign up to set email alerts
|

Foundations of SPARQL query optimization

Abstract: We study fundamental aspects related to the efficient processing of the SPARQL query language for RDF, proposed by the W3C to encode machine-readable information in the Semantic Web. Our key contributions are (i) a complete complexity analysis for all operator fragments of the SPARQL query language, which -as a central result -shows that the SPARQL operator OPTIONAL alone is responsible for the PSPACE-completeness of the evaluation problem, (ii) a study of equivalences over SPARQL algebra, including both rewri… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

3
236
0
4

Year Published

2011
2011
2024
2024

Publication Types

Select...
6
2

Relationship

1
7

Authors

Journals

citations
Cited by 237 publications
(247 citation statements)
references
References 34 publications
(151 reference statements)
3
236
0
4
Order By: Relevance
“…In [11,17], the authors study the complexity of evaluating the fragment of SPARQL consisting of the operators AND, UNION, OPT and FILTER. One of the conclusions of these papers is that the main source of complexity in SPARQL comes from the use of the OPT operator.…”
Section: Optimization Via Well-designed Patternsmentioning
confidence: 99%
See 1 more Smart Citation
“…In [11,17], the authors study the complexity of evaluating the fragment of SPARQL consisting of the operators AND, UNION, OPT and FILTER. One of the conclusions of these papers is that the main source of complexity in SPARQL comes from the use of the OPT operator.…”
Section: Optimization Via Well-designed Patternsmentioning
confidence: 99%
“…Besides, we implement the optimizations proposed in [11], using the notion of welldesigned patterns, which prove to be effective in the optimization of queries that contain the OPTIONAL operator, the most costly operator in SPARQL [11,17]. This has also important implications in the number of tuples being transferred and joined in federated queries, and hence our implementation benefits from this.…”
Section: Introductionmentioning
confidence: 99%
“…We choose SPARQL as a query language: It is known to be relationally complete, allowing us to encode a broad range of queries with varying complexity, from simple conjunctive queries to complex requests involving e.g. negation [4,20,22]. We restrict ourselves on general characteristics, pointing to the FedBench project page for a complete listing and description.…”
Section: Benchmark Queriesmentioning
confidence: 99%
“…(Q1) Query Language: The expressiveness of the query language needed by applications may vary from case to case: while some applications get around with simple conjunctive queries, others may rely on the full expressive power of RDF query languages, such as the de facto standard SPARQL [20,22]. (Q2) Result Completeness: Certain applications may rely on complete results, while others cannot afford it when responsiveness is first priority.…”
Section: Introductionmentioning
confidence: 99%
“…Existing approaches focus on algebraic [11,13] or selectivity-based optimizations [14]. Despite an increasing need from practitioners [5,6], few works address top-k query optimization in SPARQL.…”
Section: Related Workmentioning
confidence: 99%