atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sarath Subramanian (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-2308) Remove 'titan1' graph provider from atlas
Date Mon, 11 Dec 2017 18:47:00 GMT

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

Sarath Subramanian updated ATLAS-2308:
--------------------------------------
    Attachment: ATLAS-2308.1.patch

> Remove 'titan1' graph provider from atlas
> -----------------------------------------
>
>                 Key: ATLAS-2308
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2308
>             Project: Atlas
>          Issue Type: Task
>          Components:  atlas-core
>    Affects Versions: 1.0.0
>            Reporter: Sarath Subramanian
>            Assignee: Sarath Subramanian
>             Fix For: 1.0.0
>
>         Attachments: ATLAS-2308.1.patch
>
>
> We have 3 graph databases in atlas:
> 1. titan0 (Titan 0.5.4)
> 2. titan1 (Titan 1.0.0)
> 3. janus (JanusGraph 0.2.0)
> The default graph-provider is *JanusGraph* currently. I propose we remove 'titan1' graph
provider from Atlas for reasons below:
> 1. 'titan1' has not been tested thoroughly and have higher chances of potential issues.
> 2. We have moved on to use JanusGraph in Atlas which is an improved graph database forked
from Titan 1 with community support and active development going on. 
> 2. TitanDB is retired, the new project JanusGraph which is now part of the Linux foundation
has more interest and backing.
> We will continue to support 'titan0' as Titan 0.5.4 has been tested and have wider audience
within the community and also to support backward compatibility. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message