[
https://issues.apache.org/jira/browse/ATLAS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222553#comment-16222553
]
Graham Wallis commented on ATLAS-1757:
--------------------------------------
Attaching ATLAS-1757-v4.patch.
Please see RBT for details: https://reviews.apache.org/r/63041
It has been decided that we will only go as far as JanusGraph 0.1.1 for the
time being, due to needing extra migration work for JanusGraph 0.2.0, which
will happen soon.
This patch runs almost clean with JanusGraph 0.1.1, the caveat being two UT
failures in repository:
* GraphBackedMetadataRepositoryTest.testConcurrentCalls
*
AtlasRelationshipStoreV1Test.testRelationshipAttributeUpdate_NonComposite_OneToMany
> 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, 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)
