Mailing-List: contact dev-help@atlas.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@atlas.apache.org
Date: Tue, 17 Oct 2017 10:48:03 +0000 (UTC)
From: "Graham Wallis (JIRA)" <jira@apache.org>
To: dev@atlas.apache.org
Message-ID: <JIRA.13067289.1493283019000.15174.1508237283434@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: 7bit
archived-at: Tue, 17 Oct 2017 10:48:11 -0000


    [ https://issues.apache.org/jira/browse/ATLAS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207273#comment-16207273 ] 

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

A quick, general update on this JIRA.
The attached proposal doc defined 4 stages:

Stage 1: The first stage was to restructure the build files, which was in the v1 patch. This changed the graph profiles and introduced the GRAPH-PROVIDER system variable as a way of selecting graph provider. See the graphdb/readme.txt in the v2 patch for details.

Stage 2: The second stage is the introduction of JanusGraph to Atlas. The v2 patch introduces the graphdb/janus module and contains some restructuring of graphdb/common and graphdb/titan0, graphdb/titan1; so that graphdb/common applies to any tinkerpop database (of which titan0, titan1 and janus are all examples).

Work is ongoing on stage 2. At this time, the v2 patch has been built clean but not tested. I intend to start running UTs/ITs on it and fixing up problems as I find them. 

There is additional work to do for stage 2 to update any other Atlas components that are not yet at Tinkerpop3. On a recent Atlas dev call it was decided that the catalog component should be removed - this is one of the components that is back-level at Tinkerpop2. There are also other Atlas components that will need to be updated. 

There may also be further updates to exploit features of Janus and look at introducing the visibility feature described above (thanks [~hulbs] and [~jerryhe]) or to modify the Atlas SOE in line with Janus dependencies.

The desired result of stage 2 is to provide a choice between graphdb/titan0 and graphdb/janus, both of which should be fully operational.


> 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
>         Attachments: ATLAS-1757 Proposal to change graph database.pdf, ATLAS-1757-v1.patch, ATLAS-1757-v2.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)