Mailing-List: contact dev-help@atlas.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@atlas.apache.org
Date: Wed, 15 Nov 2017 09:18:00 +0000 (UTC)
From: "Graham Wallis (JIRA)" <jira@apache.org>
To: dev@atlas.apache.org
Message-ID: <JIRA.13097255.1503562216000.243222.1510737480256@Atlassian.JIRA>
In-Reply-To: <JIRA.13097255.1503562216000@Atlassian.JIRA>
References: <JIRA.13097255.1503562216000@Atlassian.JIRA> <JIRA.13097255.1503562216846@jira-lw-us.apache.org>
Subject: [jira] [Commented] (ATLAS-2084) Make berkeley DB backed Atlas
 available without external download
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 15 Nov 2017 09:18:04 -0000


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

Graham Wallis commented on ATLAS-2084:
--------------------------------------

I thought that BDB was pulled in anyway - regardless of which graph provider Atlas is using.....

> Make berkeley DB backed Atlas available without external download
> -----------------------------------------------------------------
>
>                 Key: ATLAS-2084
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2084
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Nigel Jones
>            Assignee: Nigel Jones
>         Attachments: ATLAS_2084_Add_BerkeleyDB_libraries.patch
>
>
> In https://issues.apache.org/jira/browse/ATLAS-2012 I proposed providing a dockerized version of Atlas to aid people getting up to speed with the technology. During the review it was noted that we had used Hbase for storage rather than the more lightweight, simpler, BerkeleyDB. My concern had been around licensing.
> Today when we build Atlas following the instructions at http://atlas.apache.org/InstallationSteps.html the user is directed to download the berkeleyDB jar from oracle. In ATLAS-2012 David/Graham pointed out that this DB appears to be Apache 2.0 licensed, which means we could incorporate it into our build legitimately.
> Given the necessity to get licensing correct I've opened up this new JIRA to focus on that change. We would need to
>  * Validate we are indeed correct about the license
>  * Add the DB file into the build
>  * Update the web instructions
>  * And optionally as per the original JIRA, consider making B-DB the default for our docker image (most lightweight).
> Please add your thoughts. I'm happy to get and do this change .


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