# gStoreD

**Repository Path**: liruxru/gStoreD

## Basic Information

- **Project Name**: gStoreD
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: BSD-3-Clause
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2025-03-16
- **Last Updated**: 2025-03-16

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

#gStoreD

## gStore v0.3.0-D

### Overview
gStoreD is a distributed RDF data management system (or what is commonly called a "triple store") that is based on "partial evaluation" and maintains the graph structure of the original [RDF](http://www.w3.org/TR/rdf11-concepts/) data. Its data model is a labeled, directed multiedge graph, where each vertex corresponds to a subject or an object. We also represent a given [SPARQL](http://www.w3.org/TR/sparql11-overview/) query by a query graph Q. Query processing involves finding subgraph matches of Q over the RDF graph G. 

This system has been published in two papers. 

Peng Peng, Lei Zou, Runyu Guan. Accelerating Partial Evaluation in Distributed SPARQL Query Evaluation. ICDE 2019: 112-123

Peng Peng, Lei Zou, M. Tamer Özsu, Lei Chen, Dongyan Zhao. Processing SPARQL queries over distributed RDF graphs. VLDB J. 25(2): 243-268 (2016)


### Install Steps
System Requirement: 64-bit linux server with GCC, mpich-3.0.4, make, readline installed.
*We have tested on linux server with CentOS 6.2 x86_64. The version of GCC should be 4.4.7 or later.*

You can install gStore v0.3.0-D in one command. Just run

`# make` 

to compile the gStore code and build executable "gloadD", "gqueryD".

### Usage
gStore v0.3.0-D currently includes two executables and others.

####1. gloadD
gloadD is used to build a new database from a RDF triple format file.

`# mpiexec -f host_file_name -n host_number + 1 ./gloadD db_name rdf_triple_file_name internal_vertices_file_name`

The host file is used to idenitfy the hosts. "host_number + 1" means that there should be one more process as the master site.

Each line in the file of the internal vertices consists of two parts: the first part is the URI of an resouce, and the second part is the identifier of the partition that the resouce belongs to. The tab "\t" is used as the separator.

For example, we build a database from dbpedia_example_distgStore.n3 which can be found in example folder.

    [root@master Gstore]# mpiexec -f hosts.txt -n 5 bin/gloadD db_dbpedia_example_distgStore ./example/dbpedia_example_distgStore.n3 ./example/dbpedia_example_distgStore_internal.TXT

####2. gqueryD
gqueryD is used to query an exsisting database with SPARQL files.

`mpiexec -f host_file_name -n host_number + 1 ./gqueryD db_name query_file_name`

When the program finish answering the query, the SPARQL matches are written in the file named `finalRes.txt`.

*gStorev0.3.0-D only support simple "select" queries and "ask" queries of BGP now, and all variables occuring in the "where" clause of a "select" query should also occur in the "selsect" clause.*

We also take dbpedia_example_distgStore.n3 as an example.

    [root@master Gstore]# mpiexec -f hosts.txt -n 5 bin/gqueryD db_dbpedia_example_distgStore ./example/query.txt
   
Notice: 

All results are output into finalRes.txt.

If you encounter any problems, please send emails to me (email address: hnu16pp@hnu.edu.cn).