Skip to main navigation Skip to search Skip to main content

RDFViewS: A storage tuning wizard for RDF applications

  • François Goasdoué
  • , Konstantinos Karanasos
  • , Julien Leblay
  • , Ioana Manolescu
  • INRIA
  • Sorbonne Université

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution › peer-review

4 Citations (Scopus)

Abstract

In recent years, the significant growth of RDF data used in numerous applications has made its efficient and scalable manipulation an important issue. In this paper, we present RDFViewS, a system capable of choosing the most suitable views to materialize, in order to minimize the query response time for a specific SPARQL query workload, while taking into account the view maintenance cost and storage space constraints. Our system employs practical algorithms and heuristics to navigate through the search space of potential view configurations, and exploits the possibly available semantic information - expressed via an RDF Schema - to ensure the completeness of the query evaluation.

Original languageEnglish
Title of host publicationCIKM'10 - Proceedings of the 19th International Conference on Information and Knowledge Management and Co-located Workshops
Pages1947-1948
Number of pages2
DOIs
Publication statusPublished - 1 Dec 2010
Externally publishedYes
Event19th International Conference on Information and Knowledge Management and Co-located Workshops, CIKM'10 - Toronto, ON, Canada
Duration: 26 Oct 2010 → 30 Oct 2010

Publication series

NameInternational Conference on Information and Knowledge Management, Proceedings

Conference

Conference19th International Conference on Information and Knowledge Management and Co-located Workshops, CIKM'10
Country/TerritoryCanada
CityToronto, ON
Period26/10/10 → 30/10/10

Keywords

  • Materialized views
  • Query optimization
  • RDFS
  • Rdf data management
  • View selection

Fingerprint

Dive into the research topics of 'RDFViewS: A storage tuning wizard for RDF applications'. Together they form a unique fingerprint.

Cite this