You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Nigel Jones (JIRA)" <ji...@apache.org> on 2017/10/25 10:18:00 UTC
[jira] [Commented] (ATLAS-2084) Make berkeley DB backed Atlas
available without external download
[ https://issues.apache.org/jira/browse/ATLAS-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218365#comment-16218365 ]
Nigel Jones commented on ATLAS-2084:
------------------------------------
The main Berkeley DB page is at http://www.oracle.com/technetwork/database/database-technologies/berkeleydb/overview/index.html
The latest version is 12.1.6.2.32 - pulling the tar apart we see that the library is licensed under the GNU AFFERO GENERAL PUBLIC LICENSE Version 3
Referring to https://www.apache.org/legal/resolved.html it's clear the gnu affero license IS NOT PERMITTED for being bundled with apache projects
For this reason I will have to close this JIRA - it seems we cannot include the berkeleyDB libraries within Atlas. Not a huge issue as this is primarily for devs, and other persistance options can be used.
Closing.
> 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
>
> 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)