atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Hulbert (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ATLAS-1757) Proposal to update graph DB
Date Mon, 16 Oct 2017 18:19:00 GMT

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

Andrew Hulbert edited comment on ATLAS-1757 at 10/16/17 6:18 PM:
-----------------------------------------------------------------

Is there anything on the roadmap for the future to support visibility filtering with Atlas
+ JanusGraph + HBase? For example, it would be interesting to have the ability to access control
specific vertices, attributes, or relationships based on visibilities which systems like bigtable
systems like HBase and Accumulo can support. I'd be interested to see if anyone else desires
this and if so I'd probably put a vote in for JanusGraph and contributing to help make that
a top level feature in both Atlas and JanusGraph.

On another note, I like having the Apache 2 and Hadoop-related graph implementation. There's
lots of HBase already out there so having at least 1 graph implementation on that keeps Atlas
in line with that stack.


was (Author: hulbs):
Is there anything on the roadmap for the future to support visibility filtering with Atlas
+ JanusGraph + HBase? For example, it would be interesting to have the ability to access control
specific vertices, attributes, or relationships based on visibilities which systems like bigtable
systems like HBase and Accumulo can support. I'd be interested to see if anyone else desires
this and if so I'd probably put a vote in for JanusGraph and contributing to help make that
a top level feature in both Atlas and JanusGraph.

> 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)

Mime
View raw message