[jira] [Created] (ATLAS-2210) Add relationship methods to AtlasClientV2
Andrew Hulbert created ATLAS-2210: - Summary: Add relationship methods to AtlasClientV2 Key: ATLAS-2210 URL: https://issues.apache.org/jira/browse/ATLAS-2210 Project: Atlas Issue Type: Improvement Reporter: Andrew Hulbert -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-2210) Add relationship methods to AtlasClientV2
[ https://issues.apache.org/jira/browse/ATLAS-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203989#comment-16203989 ] Andrew Hulbert commented on ATLAS-2210: --- I have started a branch: https://github.com/jahhulbert-ccri/atlas/tree/add_relationships_to_clientv2 > Add relationship methods to AtlasClientV2 > - > > Key: ATLAS-2210 > URL: https://issues.apache.org/jira/browse/ATLAS-2210 > Project: Atlas > Issue Type: Improvement >Reporter: Andrew Hulbert > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1757) Proposal to update graph DB
[ https://issues.apache.org/jira/browse/ATLAS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16206328#comment-16206328 ] Andrew Hulbert commented on ATLAS-1757: --- 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)
[jira] [Comment Edited] (ATLAS-1757) Proposal to update graph DB
[ 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)
[jira] [Commented] (ATLAS-2210) Add relationship methods to AtlasClientV2
[ https://issues.apache.org/jira/browse/ATLAS-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211125#comment-16211125 ] Andrew Hulbert commented on ATLAS-2210: --- forgot to ask...can someone assign this to me or add me with perms to do so? I think it should be all wrapped up now: https://issues.apache.org/jira/browse/ATLAS-2210 > Add relationship methods to AtlasClientV2 > - > > Key: ATLAS-2210 > URL: https://issues.apache.org/jira/browse/ATLAS-2210 > Project: Atlas > Issue Type: Improvement >Reporter: Andrew Hulbert > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1757) Proposal to update graph DB
[ https://issues.apache.org/jira/browse/ATLAS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211131#comment-16211131 ] Andrew Hulbert commented on ATLAS-1757: --- [~davidrad] I'll try to take a look over at the Virtual Data Connector pages and discussions. I think that "field-level" visibility is definitely something that's useful for what I'm working on but the "cell-level" visibility is probably (as you mentioned) not as much on the radar at the moment. But I'll try to chat with he VD connector group and see what they are thinking. We have customers that need to segregate data from different divisions and want that strong guarantee on a per "entity" basis. > 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)
[jira] [Comment Edited] (ATLAS-2210) Add relationship methods to AtlasClientV2
[ https://issues.apache.org/jira/browse/ATLAS-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211125#comment-16211125 ] Andrew Hulbert edited comment on ATLAS-2210 at 10/19/17 5:29 PM: - forgot to ask...can someone assign this to me or add me with perms to do so? I think it should be all wrapped up now: https://reviews.apache.org/r/62984/ was (Author: hulbs): forgot to ask...can someone assign this to me or add me with perms to do so? I think it should be all wrapped up now: https://issues.apache.org/jira/browse/ATLAS-2210 > Add relationship methods to AtlasClientV2 > - > > Key: ATLAS-2210 > URL: https://issues.apache.org/jira/browse/ATLAS-2210 > Project: Atlas > Issue Type: Improvement >Reporter: Andrew Hulbert > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
