[
https://issues.apache.org/jira/browse/ATLAS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210772#comment-16210772
]
David Radley commented on ATLAS-1757:
-------------------------------------
[~hulbs] A thought on your visibility suggestion. The way we are thinking about
filtering or masking is in an architecture that is being worked on in the
Virtual Data Connector (documented in the Atlas Wiki); it aspires to bring
these sort of decisions up to the business level. It does this by working with
Glossary Terms that are classified. For example a term called National
Insurance Number could be classified as a personal sensitive information.
Apache Ranger can be setup to run policies and rules against the
classifications (it can already do this against classifications applied to
assets). Governance policies can then be specified more naturally in a
technology agnostic way. The Atlas type system helps in the architecture and
lives above the Janus persistence layer.
It might be that this Janus visibility feature could fit in this Virtual Data
connector architecture; though I am not seeing how at the moment. I am sure it
could be useful for more IT orientated use cases.
> 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)
