Go to file
bookug 6224d132b3 not use git-lfs for data;add missing files in data/ and test/ 2016-03-11 15:50:11 +08:00
.debug reinit and adjust 2016-03-04 16:49:06 +08:00
.objs reinit and adjust 2016-03-04 16:49:06 +08:00
.tmp reinit and adjust 2016-03-04 16:49:06 +08:00
Bstr merge several classes; 2015-11-06 19:13:39 +08:00
Database result direction 2016-01-25 01:43:18 -05:00
KVstore merge several classes; 2015-11-06 19:13:39 +08:00
Main reinit and adjust 2016-03-04 16:49:06 +08:00
Parser merge several classes; 2015-11-06 19:13:39 +08:00
Query reinit and adjust 2016-03-04 16:49:06 +08:00
Server update the server/client;add missing makefiles for api 2016-03-08 19:48:00 +08:00
Signature merge several classes; 2015-11-06 19:13:39 +08:00
Triple 1. use the new encode function encodeRDF_new() to replace the old one; 2015-02-02 02:53:47 -05:00
Util close Stream temporalily for debug 2016-03-06 17:20:01 +08:00
VSTree merge several classes; 2015-11-06 19:13:39 +08:00
api update the server/client;add missing makefiles for api 2016-03-08 19:48:00 +08:00
data not use git-lfs for data;add missing files in data/ and test/ 2016-03-11 15:50:11 +08:00
docs add missing jpg, docx, pdf 2016-03-09 14:54:30 +08:00
lib reinit and adjust 2016-03-04 16:49:06 +08:00
test not use git-lfs for data;add missing files in data/ and test/ 2016-03-11 15:50:11 +08:00
tools add missing files 2016-03-11 15:36:05 +08:00
.gitattributes not use git-lfs for data;add missing files in data/ and test/ 2016-03-11 15:50:11 +08:00
.gitignore fix api and build docs 2016-03-04 17:20:19 +08:00
LICENSE add BSD New license. 2015-04-23 03:50:31 -04:00
README.md not use git-lfs for data;add missing files in data/ and test/ 2016-03-11 15:50:11 +08:00
makefile add missing files 2016-03-11 15:36:05 +08:00

README.md

Gstore System

Gstore System(also called gStore) is a graph database engine for managing large graph-structured data, which is open-source and targets at Linux operation systems. The whole project is written in C++, and we try our best to avoid using STL. Only source tarballs are provided currently, which means you have to compile the source code if you want to use our system.

Getting Started

This system is really user-friendly and you can pick it up in several minutes. Remember to check your platform where you want to run this system by viewing System Requirements. After all are verified, please get this project's source code. There are several ways to do this:

  • download the zip from this repository and extract it

  • fork this repository in your github account

  • type git clone git@github.com:Caesar11/gStore.git in your terminal or use git GUI to acquire it

Then you need to compile the project, just type make in the gStore root directory, and all executables will be ok. To run gStore, please type ./gload database_name dataset_path to build a database named by yourself. And you can use ./gquery database_name command to query a existing database.

**Notice: Some files(*.jpg, *.docx, .pdf) in the docs/ folder, and files of .tar.gz type in the test/ folder are stored using Git Large File Storage, you need to install git-lfs to clone/download if you want to include them in the project. Do not care it if you do not want to see them.


Advanced Help

If you want to understand the details of the gStore system, or you want to try some advanced operations(for example, using the API, server/client), please see the chapters below.


Other Business

We have written a series of short essays addressing recurring challenges in using gStore to realize applications, which are placed in Recipe Book.

You are welcome to report any advice or errors in the github Issues part of this repository, if not requiring in-time reply. However, if you want to urgent on us to deal with your reports, please email to chenjiaqi93@163.com to submit your suggestions and report bugs to us by emailing to zengli-syzz@pku.edu.cn. A full list of our whole team is in Mailing List.

There are some restrictions when you use the current gStore project, you can see them on Limit Description.

Sometimes you may find some strange phenomena(but not wrong case), or something hard to understand/solve(don't know how to do next), then go to the Frequently Asked Questions page.

Graph database engine is a new area and we are still trying to go further. Things we plan to do next is in Future Plan chapter, and we hope more and more people will support or even join us. You can support in many ways:

  • watch/star our project

  • fork this repository and submit pull requests to us

  • download and use this system, report bugs or suggestions

  • ...

People who inspire us or contribute to this project will be listed in the Thanks List chapter.