atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Graham Wallis (JIRA)" <>
Subject [jira] [Commented] (ATLAS-1757) Proposal to update graph DB
Date Tue, 12 Dec 2017 10:44:00 GMT


Graham Wallis commented on ATLAS-1757:

Brief update on graph changes to Atlas - most of the work proposed in this JIRA is now complete.
* ATLAS-2264 updated JanusGraph to 0.2.0 []
* ATLAS-2308 removed titan1 []
With these JIRAs, Atlas supports JanusGraph 0.2.0 (tinkerpop3) and Titan 0.5.4 (tinkerpop2).
The parts (of ATLAS-1757) that were not completed are removal of the titan0 profile (which
will happen at some point in the future under a separate JIRA) and the possible option of
building with multiple providers and selecting provider via configuration, (which is less
likely to happen).
[ATLAS-2270] contains a discussion of choice of persistence and indexing backends.

> Proposal to update graph DB
> ---------------------------
>                 Key: ATLAS-1757
>                 URL:
>             Project: Atlas
>          Issue Type: Improvement
>          Components:  atlas-core
>    Affects Versions: trunk
>            Reporter: Graham Wallis
>            Assignee: Graham Wallis
>             Fix For: 1.0.0
>         Attachments: ATLAS-1757 Proposal to change graph database.pdf, ATLAS-1757-v1.patch,
ATLAS-1757-v2.patch, ATLAS-1757-v3.patch, ATLAS-1757-v4.patch
> Given the formation of the JanusGraph open source project (under the Linux Foundation)
to continue the development and support of the Titan DB, should we aim to deprecate Titan
and move over to JanusGraph?
> If we did this, we could keep the graph abstraction layer and use it to support Titan
0, Titan 1 and JanusGraph.
> Are there other graph databases that we should consider?

This message was sent by Atlassian JIRA

View raw message