databrickslabs / databrickslabs/ontos
[Feature]: Support pluggable graph storage engines for the ontologies
Open
Nobody has claimed this yet.
scope/ontology
type/feature
- Dominant language
- Python
- Stars
- 212
- Forks
- 71
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 43
Description
Is there an existing issue for this?
- I have searched the existing issues
Problem statement
The graph is stored in a relational table and loaded into memory. We need to support scalable backends for larger setups.
Proposed Solution
Support a pluggable storage backend for the RDF-based graph. Ideally a graph-based service, so that SPARQL queries could directly run on the extermal system.
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by mapping the existing relational-table graph storage and its loading path, then define the backend boundary and verify that an external RDF graph service can be selected and queried directly with SPARQL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100