Join processing in relational databases
ACM Computing Surveys (CSUR)
A relational model of data for large shared data banks
Communications of the ACM
Fundamentals of Database Systems
Fundamentals of Database Systems
A new way to compute the product and join of relations
SIGMOD '80 Proceedings of the 1980 ACM SIGMOD international conference on Management of data
Sesame: A Generic Architecture for Storing and Querying RDF and RDF Schema
ISWC '02 Proceedings of the First International Semantic Web Conference on The Semantic Web
Database Systems: An Application Oriented Approach, Complete Version (2nd Edition)
Database Systems: An Application Oriented Approach, Complete Version (2nd Edition)
SPARQL query processing with conventional relational database systems
WISE'05 Proceedings of the 2005 international conference on Web Information Systems Engineering
Semantics preserving SPARQL-to-SQL translation
Data & Knowledge Engineering
Towards efficient join processing over large RDF graph using mapreduce
SSDBM'12 Proceedings of the 24th international conference on Scientific and Statistical Database Management
Hi-index | 0.00 |
Increasing amount of RDF data on the Web drives the need for its efficient and effective management. In this light, numerous researchers have proposed to use RDBMSs to store and query RDF annotations using the SQL and SPARQL query languages. The first few attempts at SPARQL-to-SQL translation revealed non-trivial challenges related to correctness and efficiency of such translation in the presence of nested optional graph patterns. In this paper, we propose to extend relational databases with a novel relational operator, nested optional join (NOJ), that is more efficient than left outer join in processing nested optional graph patterns. We design three efficient algorithms to implement the new operator in relational databases: (1) nested-loops NOJ algorithm, NL-NOJ, (2) sort-merge NOJ algorithm, SM-NOJ, and (3) simple hash NOJ algorithm, SH-NOJ. Based on a real life RDF dataset, we demonstrate the efficiency of our algorithms by comparing them with the corresponding left outer join implementations.