[
https://issues.apache.org/jira/browse/ATLAS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved ATLAS-40.
-----------------------------------
Resolution: Won't Do
Resolving as there hasn't been any update on this enhancement for more than 4
years.
> Support Accumulo as persistent store for graph repository
> ---------------------------------------------------------
>
> Key: ATLAS-40
> URL: https://issues.apache.org/jira/browse/ATLAS-40
> Project: Atlas
> Issue Type: Improvement
> Affects Versions: 0.5-incubating
> Reporter: Russ Weeks
> Assignee: Russ Weeks
> Priority: Minor
>
> I'd like to work on supporting [Accumulo|http://accumulo.apache.org] as well
> as HBase as a persistent store for the code in org.apache.atlas.repository.
> I can see two ways that this could work:
> # Define a new GraphProvider and provide an implementation of the Tinkerpop
> blueprints Graph which is backed by Accumulo - there are several good options
> here like
> [Calrissian|https://github.com/calrissian/accumulo-recipes/tree/master/store/graph-store]
> or the [JHU APL implementation|https://github.com/JHUAPL/AccumuloGraph].
> # Implement a new [Titan storage
> backend|https://github.com/thinkaurelius/titan/wiki/Storage-Backend-Overview]
> that writes to Accumulo. Any changes to Atlas should be limited to Titan
> configuration (probably some Accumulo-specific parameters).
> Would this improvement be welcome? If so, can somebody suggest the best way
> to proceed? I was looking at option #1 originally but it looks like some
> parts of the code (eg.
> [GraphBackedMetadataRepository|https://github.com/apache/incubator-atlas/blob/6b33bcf647264131cf5b37838485675d2ed9c017/repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java#L87]
> have explicit dependencies on TitanGraph, not the Tinkerpop Graph interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
