atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russ Weeks (JIRA)" <>
Subject [jira] [Created] (ATLAS-40) Support Accumulo as persistent store for graph repository
Date Wed, 01 Jul 2015 00:23:04 GMT
Russ Weeks created ATLAS-40:

             Summary: Support Accumulo as persistent store for graph repository
                 Key: ATLAS-40
             Project: Atlas
          Issue Type: Improvement
    Affects Versions: 0.5-incubating
            Reporter: Russ Weeks
            Priority: Minor
             Fix For: 0.6-incubating

I'd like to work on supporting [Accumulo|] 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|]
or the [JHU APL implementation|].
# Implement a new [Titan storage backend|]
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|]
have explicit dependencies on TitanGraph, not the Tinkerpop Graph interface.

This message was sent by Atlassian JIRA

View raw message