You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Sarath Subramanian (JIRA)" <ji...@apache.org> on 2017/10/27 21:19:01 UTC

[jira] [Resolved] (ATLAS-1757) Proposal to update graph DB

     [ https://issues.apache.org/jira/browse/ATLAS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sarath Subramanian resolved ATLAS-1757.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

Thanks for the patch [~grahamwallis].

Committed to master: http://git-wip-us.apache.org/repos/asf/atlas/commit/503dddb8

> Proposal to update graph DB
> ---------------------------
>
>                 Key: ATLAS-1757
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1757
>             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
(v6.4.14#64029)