Mailing-List: contact dev-help@atlas.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@atlas.incubator.apache.org
Date: Fri, 28 Apr 2017 09:20:04 +0000 (UTC)
From: "Graham Wallis (JIRA)" <jira@apache.org>
To: dev@atlas.incubator.apache.org
Message-ID: <JIRA.13067289.1493283019000.76962.1493371204776@Atlassian.JIRA>
In-Reply-To: <JIRA.13067289.1493283019000@Atlassian.JIRA>
References: <JIRA.13067289.1493283019000@Atlassian.JIRA> <JIRA.13067289.1493283019353@jira-lw-us.apache.org>
Subject: [jira] [Commented] (ATLAS-1757) Proposal to update graph DB
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 28 Apr 2017 09:20:11 -0000


    [ https://issues.apache.org/jira/browse/ATLAS-1757?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1598=
8499#comment-15988499 ]=20

Graham Wallis commented on ATLAS-1757:
--------------------------------------

There are quite a few graph databases that might be worthy of consideration=
. I think it is reasonable to suggest that we limit our attention to those =
that have Apache-2 licensed APIs and that include support for Tinkerpop 3.2=
. The latter restriction appears to eliminate ArangoDB, OrientDB and Gaffer=
 but leaves JanusGraph and Neo4j as candidates. JanusGraph is the more obvi=
ous candidate as it is Apache-2 licensed throughout and (as noted in the ar=
ticles linked above) could be considered to be the reference implementation=
 of TP3. Whilst less obvious, Neo4j includes an Apache-2 licensed API libra=
ry - neo4j-gremlin - that does not include the GPL3-licensed implementation=
 of neo4j. We could adopt the above as our forward-looking strategy but I w=
ould be keen that we chip away at this - e.g. by adding JanusGraph via the =
graph abstraction layer and (at some point) making it the default and depre=
cating the use of Titan 0 and Titan 1. Other graph databases (e.g. neo4j-gr=
emlin) could be added via the graph abstraction layer depending on users' r=
equirements.

> 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
>
> Given the formation of the JanusGraph open source project (under the Linu=
x Foundation) to continue the development and support of the Titan DB, shou=
ld 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 s=
upport Titan 0, Titan 1 and JanusGraph.
> Are there other graph databases that we should consider?


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)