atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Radley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-2270) Supported combinations of persistent store and index backend
Date Mon, 20 Nov 2017 16:47:00 GMT

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

David Radley commented on ATLAS-2270:
-------------------------------------

[~grahamwallis] thanks or raising this Jira. 
I suggest we consider: 
- do we support external or only imbedded backing stores for titan0 and Janus. 
- The generated configs should work with the built code.
- ideally we should remove anything that the user cannot customise from the config. For example
whether we are Titan0 or Janus, Solr or ES, Hbase or Berkeley. 
- All unsupported maven options should fail gracefully.
- we should remove all mention of titan1 and Janus 0.1.1. in the code, comments and docs.

     


> Supported combinations of persistent store and index backend
> ------------------------------------------------------------
>
>                 Key: ATLAS-2270
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2270
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Graham Wallis
>
> We need to discuss and decide which combinations of persistent store and indexing backend
Atlas 1.0.0 (master) should support. This includes building/running Atlas as a standalone
package and running UTs/ITs as part of the Atlas build. 
> This JIRA focusses on titan0 and janusgraph 0.2.0, as they are the graph databases that
will be supported in master/1.0.0. This JIRA deliberately ignores titan1 and janusgraph 0.1.1
as the former should be deprecated/removed and the other is a transient state as we get to
janusgraph 0.2.0. 
> With titan0 as the graph provider, Atlas has supported the following combinations of
persistent store and indexer. It is suggested that this set is kept unchanged:
> {{
> titan0              solr          es
> ------------------------------------
> berkeley           0              1
> hbase               1              0
> cassandra        0              0
> }}
> With janusgraph (0.2.0) as the graph provider, Atlas *could* support additional combinations.
Cassandra is included in this discussion pending response to ATLAS-2259.
> {{
> janus 0.2.0      solr          es
> ------------------------------------
> berkeley           ?              1
> hbase               1              ?
> cassandra        ?              ?
> }}
> It is suggested that the combinations marked with '1' should be continued and the remaining
4 combinations, marked with '?', should be considered. There seems to be evidence of people
using all 4 of these combinations, although not necessarily with Atlas.
> Depending on the decision made above, we need to ensure that it is possible to build
Atlas as a standalone package with any of the combinations - i.e. that they are mutually exclusive
and do not interfere with one another. They currently interfere which makes it impossible
to build Atlas with -Pdist,berkeley-elasticsearch because the 'dist' profile will exclude
jars that are needed by the berkeley-elasticsearch profile - which leads to class not found
exceptions when the Atlas server is started. The solution to this could be very simple, or
slightly more sophisticated, depending on how many of the combinations we choose to support.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message