[
https://issues.apache.org/jira/browse/ATLAS-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218648#comment-16218648
]
Nigel Jones commented on ATLAS-2084:
------------------------------------
Made changes to the distro/pom.xl to define a pom delta specific to the
berkeleydb-elasticsearch profile to use Oracle maven repo, but it turns out the
repo requires authentication via an oracle id - not acceptable for our generic
build. Therefore the only option is to include the .jar (which should be fine
as it's ASF 2.0 licensed). Plan B ...
> 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
>
> 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)
