Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 43F90200D4B for ; Mon, 27 Nov 2017 19:32:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 429E9160C13; Mon, 27 Nov 2017 18:32:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 88E5A160BFA for ; Mon, 27 Nov 2017 19:32:03 +0100 (CET) Received: (qmail 95605 invoked by uid 500); 27 Nov 2017 18:32:02 -0000 Mailing-List: contact dev-help@atlas.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@atlas.apache.org Delivered-To: mailing list dev@atlas.apache.org Received: (qmail 95594 invoked by uid 99); 27 Nov 2017 18:32:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Nov 2017 18:32:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E1864C4D4B for ; Mon, 27 Nov 2017 18:32:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.011 X-Spam-Level: X-Spam-Status: No, score=-99.011 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KB_WAM_FROM_NAME_SINGLEWORD=0.2, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id TdQkakI3bU9d for ; Mon, 27 Nov 2017 18:32:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D48C95F21E for ; Mon, 27 Nov 2017 18:32:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 57805E00CD for ; Mon, 27 Nov 2017 18:32:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 10369241A0 for ; Mon, 27 Nov 2017 18:32:00 +0000 (UTC) Date: Mon, 27 Nov 2017 18:32:00 +0000 (UTC) From: "Pierre Padovani (JIRA)" To: dev@atlas.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ATLAS-2270) Supported combinations of persistent store and index backend MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 27 Nov 2017 18:32:04 -0000 [ https://issues.apache.org/jira/browse/ATLAS-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267205#comment-16267205 ] Pierre Padovani commented on ATLAS-2270: ---------------------------------------- Not everyone wants to be tied to using Hadoop/HDFS as part of their infrastructure. :D The issue I linked to contains the changes required to the pom.xml for Janus to enable Cassandra support. The only other thing needed is documentation around how to set it up. I've built up standalone docker images that contain: - zookeeper - cassandra - Elasticsearch - atlas (Janus 0.1.0 - working to build 0.2.0 now) We currently deploy these images for development while we prepare to roll Atlas in this same configuration. I'm happy to contribute what else may be needed in this regard. > 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)