[jira] [Commented] (ATLAS-2270) Supported combinations of persistent store and index backend

["David Radley (JIRA)" <ji...@apache.org>]

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

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

[~ppadovani]  - as far as I am aware there is no one working on this at the moment. The only permutation that works is the Hbase solr one at the moment in master. You could become a contribute and contribute a fix, which we could commit.  I think in these situations the person who would like it in, needs to contribute the fix and would then fix any issues in that stack. At this time , this stack is not a priority at the moment for the few committers I have talked to. Is this patch something you want to contribute i.e. provide a patch to master and submit on the review board and be up for fixing any issues in that stack. I so I could commit it for you if it does not break the hbase solr config. 

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)